Hi committers, Since there are two releases inprogress, there are a few notes to keep in mind:
- all the new code should be merged into master first, mark it as milestone `4.7.0` and label it as `release/4.7.0`. - if code needs to be included in release 4.6.0, when you merge a pull request, we need to cherry-pick it to 4.6.0. The merge script does cherry-pick for you if you just follow the instructions. - Sijie On Fri, Nov 3, 2017 at 6:15 PM, Sijie Guo <guosi...@gmail.com> wrote: > lgtm +1 > > well done, Jia! > > - Sijie > > On Fri, Nov 3, 2017 at 5:37 PM, Jia Zhai <zhaiji...@gmail.com> wrote: > >> Hi all, >> Updating, FYI: >> The new milestone and labels for 4.7.0, and release branch-4.6 have been >> created: >> https://github.com/apache/bookkeeper/labels/release%2F4.7.0 >> https://github.com/apache/bookkeeper/milestone/3 >> https://github.com/apache/bookkeeper/tree/branch-4.6 >> >> I will go through the opened 4.6.0 tasks: >> https://github.com/apache/bookkeeper/issues?q=is%3Aissue+is% >> 3Aopen+label%3Arelease%2F4.6.0 >> and will move most of them into 4.7.0. >> If you have issues that need to be included for 4.6.0, please help label >> them as “release/4.6.0” and milestone “4.6.0", and also label them as >> blocker or important. >> >> Thanks. >> >> On Fri, Nov 3, 2017 at 10:32 AM, Jia Zhai <zhaiji...@gmail.com> wrote: >> >> > Hi all, >> > According to the release plan of apache bookkeeper, I would like to >> call a >> > code freeze for release 4.6.0. >> > >> > 1, We will create new branch this weekend. >> > 2, No more feature issue should be marked as 4.6.0; any new feature >> should >> > be marked as 4.7.0. >> > 3, Bug fix issues, which are really needed, could still be OK to get in, >> > in future 2 weeks. >> > 4, We will prepare 4.6.0 branch for release soon, the documentation >> work >> > for 4.6.0 will start next week. >> > >> > Regards. >> > -Jia >> > >> > >
