<div dir="ltr">+1<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 4, 2017 at 8:04 PM, Matt S Trout <span dir="ltr"><<a href="mailto:mst@shadowcat.co.uk" target="_blank">mst@shadowcat.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">(obviously, "fix any bugs we find while testing" should be taken as read)<br>
<br>
I have a few areas of concern wrt the changes made since last release:<br>
<br>
1) The sanitychecker code is going to point out a lot of things that were<br>
only ever accidentally working - but many of those things may continue to<br>
accidentally work, and if it barfs valid-but-numerous warnings all over<br>
people's log files that may discourage people upgrading who would, on the<br>
whole, be better upgrading anyway (and while most of the changes to the<br>
internals were in prior releases, people have this tendency not to upgrade<br>
as often as I would ideally like). Note: this may be me being pointlessly<br>
paranoid, but I'd like some experience reports from users to try and gauge<br>
it by before I file it under "we should just tell them to stop worrying and<br>
learn to love the sanity checker".<br>
<br>
2) A different class of 'accidentally working' requires the addition of<br>
attributes to methods, and I suspect that, for people who (a) are using<br>
method modifiers (b) are using anything else that doesn't set attributes<br>
normally (c) just hate attributes, we should provide an alternative interface<br>
that lets them do it a different way. This may be as simple as documenting<br>
that you're allowed to call attributes::import instead, though since I've got<br>
at least one foot in category (c) above I think I'd prefer something that<br>
isn't *dependent* on the attributes system and merely allows the use of<br>
attributes as one possible interface to it.<br>
<br>
3) Check through outstanding branches for things that are sufficiently<br>
low impact and/or high value that didn't make it into master but should<br>
probably do so by release time.<br>
<br>
4) Check RT for bugs that have come up during our unfortunate hiatus that<br>
are important enough we should consider rolling fixes for them into the<br>
release.<br>
<br>
5) Anything else the list membership can think of that I haven't.<br>
<br>
These all seem like things we can discuss while the devrel's soaking - though<br>
for (1) and (2) I guess people are going to want to actually play with the<br>
devrel, and everybody's opinions being basically 'mu' until they start doing<br>
so is fine by me.<br>
<br>
But, roughly, what I'm thinking is our process should be:<br>
<br>
* another devrel that at least starts to cover 3/4<br>
* ask people who're adventurous to try that one and have opinions about 1/2<br>
* decide what if anything should be done about 1/2<br>
* roll a 'this might become an RC' devrel with the results of 1-4<br>
* see what everybody thinks of that one<br>
* plan path towards a stable release<br>
<br>
Of course, category 5 could easily result in comments that make this<br>
process need a complete redo.<br>
<br>
Thoughts from the list on the above would be very welcome, or if your<br>
thought is "looks basically reasonable" then a +1 would be nice (once there's<br>
3 or 4 such replies there's no need to add to them, but I'd at least like to<br>
know "some people think it looks basically reasonable" if that's the case).<br>
<br>
--<br>
Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue<br>
<br>
<a href="http://shadowcat.co.uk/blog/matt-s-trout/" rel="noreferrer" target="_blank">http://shadowcat.co.uk/blog/<wbr>matt-s-trout/</a> <a href="http://twitter.com/shadowcat_mst/" rel="noreferrer" target="_blank">http://twitter.com/shadowcat_<wbr>mst/</a><br>
<br>
Email me now on mst (at) <a href="http://shadowcat.co.uk" rel="noreferrer" target="_blank">shadowcat.co.uk</a> and let's chat about how our CPAN<br>
commercial support, training and consultancy packages could help your team.<br>
<br>
______________________________<wbr>_________________<br>
List: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class" rel="noreferrer" target="_blank">http://lists.scsys.co.uk/cgi-<wbr>bin/mailman/listinfo/dbix-<wbr>class</a><br>
IRC: <a href="http://irc.perl.org#dbix-class" rel="noreferrer" target="_blank">irc.perl.org#dbix-class</a><br>
SVN: <a href="http://dev.catalyst.perl.org/repos/bast/DBIx-Class/" rel="noreferrer" target="_blank">http://dev.catalyst.perl.org/<wbr>repos/bast/DBIx-Class/</a><br>
Searchable Archive: <a href="http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk" rel="noreferrer" target="_blank">http://www.grokbase.com/group/<wbr>dbix-class@lists.scsys.co.uk</a><br>
</blockquote></div><br></div></div>