Hi committers,
I would like to call a code freeze for 4.6.0 now.
Now branch-4.6 ONLY accept fixes for blocking issues. Onwards pull requests
if it is not marked for 4.6, they should be merged into master branch only.
Thanks a lot.
On Wed, Nov 8, 2017 at 4:31 AM, Sijie Guo wrote:
> Hi committer
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 ne
lgtm +1
well done, Jia!
- Sijie
On Fri, Nov 3, 2017 at 5:37 PM, Jia Zhai 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/
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.
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, co
