vincent@massol.net
2014-10-15 15:21:55 UTC
Hi devs,
We’ve just released 6.2.2 and we had 51 issues fixed (in 2 weeks). What this means is that we haven’t stabilized 6.2.x yet…
Thus I’m proposing to plan ahead a 6.2.3 release.
I propose to release 6.2.3 in 2 weeks time, i.e. for the 29th of October (Note: it’s about the same time as the 6.3M2 release). If there are not enough issues in it, we can always decide to cancel it but, unfortunately, I doubt that...
What this also means is that we should continue backporting important bugs on the stable-6.2.x branch.
We now have a strategy for finding RMs but I’m also ok to perform this release myself if need be.
WDYT?
Thanks
-Vincent
We’ve just released 6.2.2 and we had 51 issues fixed (in 2 weeks). What this means is that we haven’t stabilized 6.2.x yet…
Thus I’m proposing to plan ahead a 6.2.3 release.
I propose to release 6.2.3 in 2 weeks time, i.e. for the 29th of October (Note: it’s about the same time as the 6.3M2 release). If there are not enough issues in it, we can always decide to cancel it but, unfortunately, I doubt that...
What this also means is that we should continue backporting important bugs on the stable-6.2.x branch.
We now have a strategy for finding RMs but I’m also ok to perform this release myself if need be.
WDYT?
Thanks
-Vincent