Hi everyone, The following is my current plan and proposal how to handle the '2.0' and 'master' branches leading up to 2.0 release. Please respond if I overlooked something. You can find the current 2.0 release schedule here:
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+2.0#Jenkins2.0-RoughTimeline March 23: We're aiming for the 2.0 beta release from the '2.0' branch later today. 'master' has been merged into '2.0' earlier today. --- March 27(ish): Release of Jenkins 1.655 from 'master'. This will be the last release of the 1.x line (see March 30). --- March 30: In one week, 'master' will again be merged into '2.0'. This will be released as 2.0 RC from the '2.0' branch. Ideally we're not going to merge crazy stuff into 'master' between now and next Wednesday to keep the risk of the 2.0 RC being terrible low. Any unmerged pull requests against '2.0' will be closed, and '2.0' will be merged into 'master'. This means that from that point on, anything happening on the 'master' branch will be released as 2.1, as it makes no sense to continue releasing 1.x weeklies while 2.0 code is frozen and we're preparing the release. Pull requests targeting 2.1 and beyond should be opened against 'master'. --- April 3: This weekly release will be skipped. --- April 6: Release 2.0 from the '2.0' branch (unless a critical bug is found in RC, of course). Merge '2.0' into 'master'. --- April 10(ish): Release 2.1 from the 'master' branch. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/881041A7-7532-491E-B073-3A7CDC72C25B%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
