Steve Hay
2015-07-25 11:30:19 UTC
Apologies for running a little late on this. The release schedule advertises 5.20.3 for July, but it's clearly not going to make that now. However, I hope to have it done in August, and 5.22.1 should hopefully still be on schedule in September.
To that end I have spent some time over the last week looking through all the commits since 5.20.2 and have drawn up a list of possible cherry-picks:
http://perl5.git.perl.org/perl.git/blob/refs/heads/maint-5.20-votes:/Porting/cherry-pick-votes-maint-5.20.xml
(I have done a dry-run of cherry-picking them and they are all pickable, albeit with some minor conflict resolution in some of them. I have already rejected commits that required anything non-trivial to adapt to maint-5.20's source code.)
In line with the updates to perlpolicy following the release of 5.20.2 there are not as many commits listed this time, particularly in the documentation area, so I hope they won't be too much of a burden for people to look through. I would be very grateful if some committers could spare a little time to cast their votes one way or the other.
Note that there are a lot of fixes for crashing bugs that were found by 'fuzzing' with AFL (http://lcamtuf.coredump.cx/afl/). Is it fair to say that most of these are pretty obscure corner cases that real users would be unlikely to encounter in practice? If so then perhaps we should axe them from the voting list to reduce the number of commits being pulled into maint-5.20? (I have listed them separately from other fixes to make this easier if required.)
Another two (db5cc3ee5b and #123554) could also potentially get the chop since they caused concerns and accordingly didn't make it into 5.20.2. Has anything changed to make them suitable for 5.20.3?
To that end I have spent some time over the last week looking through all the commits since 5.20.2 and have drawn up a list of possible cherry-picks:
http://perl5.git.perl.org/perl.git/blob/refs/heads/maint-5.20-votes:/Porting/cherry-pick-votes-maint-5.20.xml
(I have done a dry-run of cherry-picking them and they are all pickable, albeit with some minor conflict resolution in some of them. I have already rejected commits that required anything non-trivial to adapt to maint-5.20's source code.)
In line with the updates to perlpolicy following the release of 5.20.2 there are not as many commits listed this time, particularly in the documentation area, so I hope they won't be too much of a burden for people to look through. I would be very grateful if some committers could spare a little time to cast their votes one way or the other.
Note that there are a lot of fixes for crashing bugs that were found by 'fuzzing' with AFL (http://lcamtuf.coredump.cx/afl/). Is it fair to say that most of these are pretty obscure corner cases that real users would be unlikely to encounter in practice? If so then perhaps we should axe them from the voting list to reduce the number of commits being pulled into maint-5.20? (I have listed them separately from other fixes to make this easier if required.)
Another two (db5cc3ee5b and #123554) could also potentially get the chop since they caused concerns and accordingly didn't make it into 5.20.2. Has anything changed to make them suitable for 5.20.3?