Wei might have a point, however: 1-We still have blockers, and one is unassigned, the others are on Wilder’s plate. So there is still work to get done on the blockers and work to help Wilder.
2-If you don’t work on blockers you can start testing master as if it was RC and getting ready to vote, you might uncover other blockers 3-We have tons of PR that need reviews, and issues that need triage. So taking bit of time to look at JIRA and clean up will be a great bonus to the project. 4-if you still don’t know what to do :) you can keep working on your new features for 4.7 and make sure they are rebased, with unit tests and new marvin tests to get ready to merge. 5-if you still don’t know what to do, you might help with release notes and documentation to be ready for 4.6 release. 6-if all that is unexciting you can prepare the upgrade path. How we do it is up for grabs. I think there will be a 4.6 branch once the RC passes. -seb > On Oct 13, 2015, at 10:15 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote: > > Hi, we have the same under has Boris where all new release would be done on > master. Do we have any wikipage explaining the new release cycle, Wei have > a good point... > > Cheers, > On Oct 13, 2015 15:57, "Wei ZHOU" <ustcweiz...@gmail.com> wrote: > >> Dear Boris, >> >> Thanks for your quick reply. >> so maybe no 4.6.1 in the future? >> >> >> >> 2015-10-13 20:47 GMT+01:00 Boris Schrijver <bo...@pcextreme.nl>: >> >>> Dear Wei. >>> >>> In the new release process we are releasing directly from master. So no >> 4.6 >>> branch will be created. >>> >>> As we are releasing directly from master, it is now frozen till release. >>> >>> -- >>> >>> Met vriendelijke groet / Kind regards, >>> >>> Boris Schrijver >>> >>> PCextreme B.V. >>> >>> http://www.pcextreme.nl/contact >>> Tel direct: +31 6 33784542 >>> >>>> >>>> On October 13, 2015 at 9:26 PM Wei ZHOU <ustcweiz...@gmail.com> >>> wrote: >>>> >>>> >>>> Guys, >>>> >>>> As I know, 4.6 will be close to RC. I am wondering if it is time to >>> create >>>> 4.6 branch, so that we can add the upgrade path to next version and >>> new >>>> features/improvements can be merged into master branch (to keep a >>> clean >>>> 4.6 >>>> branch). >>>> >>>> By the way, which is the new version? 4.7 or 5.0 ? >>>> >>>> >>>> -Wei >>>> >>> >>
