Re: [DISCUSS] Release 4.6.0 and 4.5.1

Il sab 12 ago 2017, 04:35 Jia Zhai ha scritto: > Hi, > I would like to have a a try on 4.6.0. > > On Sat, Aug 12, 2017 at 10:25 AM, Sijie Guo wrote: > > > 4.5.0 is out. Although we haven't reached a conclusion whether we want to > > adopt "Time Based Release Plan" yet, I would still like to star

[GitHub] zhaijack commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

zhaijack commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321953124 @sijie Thanks a lot for the work. And I have verified 4.5.0 image. it worked well. -

Re: [DISCUSS] Release 4.6.0 and 4.5.1

Hi, I would like to have a a try on 4.6.0. On Sat, Aug 12, 2017 at 10:25 AM, Sijie Guo wrote: > 4.5.0 is out. Although we haven't reached a conclusion whether we want to > adopt "Time Based Release Plan" yet, I would still like to start the > discussion on the next releases. > > The next *featur

[DISCUSS] Release 4.6.0 and 4.5.1

4.5.0 is out. Although we haven't reached a conclusion whether we want to adopt "Time Based Release Plan" yet, I would still like to start the discussion on the next releases. The next *feature* release will be 4.6.0 and we will probably have a bug fix 4.5.1 for branch 4.5. all the features will g

[GitHub] sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321949702 cherry-picked all docker related to changes to both `branch-4.5` and `release-4.5.0` (retagged). 4.5.0 image is built - https://hub.docke

[GitHub] sijie opened a new issue #440: Update "who we are?" page

sijie opened a new issue #440: Update "who we are?" page URL: https://github.com/apache/bookkeeper/issues/440 Why? - we have DL PPMC members joining BK PMC - update JV's name to full name "Venkateswararao (JV) Jujjuri" -

[GitHub] sijie closed pull request #386: Issue-385 Upgrade to commons-lang 2.6

sijie closed pull request #386: Issue-385 Upgrade to commons-lang 2.6 URL: https://github.com/apache/bookkeeper/pull/386 This is an automated message from the Apache Git Service. To respond to the message, please log on GitH

[GitHub] sijie closed issue #385: Upgrade to commons-lang 2.6

sijie closed issue #385: Upgrade to commons-lang 2.6 URL: https://github.com/apache/bookkeeper/issues/385 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the

[GitHub] sijie closed pull request #436: Issue 418: bump docker to use bk - 4.5.0

sijie closed pull request #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436 This is an automated message from the Apache Git Service. To respond to the message, please log on G

[GitHub] sijie closed issue #418: Bump Docker to use 4.5.0 binarary

sijie closed issue #418: Bump Docker to use 4.5.0 binarary URL: https://github.com/apache/bookkeeper/issues/418 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and us

[GitHub] sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321933396 merging this now. - merge this to both master and branch-4.5 - git checkout a new branch from tag `release-4.5.0` (because it was creat

[GitHub] sijie closed issue #435: Build javadoc for releases

sijie closed issue #435: Build javadoc for releases URL: https://github.com/apache/bookkeeper/issues/435 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the U

[GitHub] sijie closed pull request #438: Issue 435: Build javadoc for releases

sijie closed pull request #438: Issue 435: Build javadoc for releases URL: https://github.com/apache/bookkeeper/pull/438 This is an automated message from the Apache Git Service. To respond to the message, please log on GitH

[GitHub] sijie commented on issue #221: TestAuth#testCloseMethodCalledOnAuthProvider is failing

sijie commented on issue #221: TestAuth#testCloseMethodCalledOnAuthProvider is failing URL: https://github.com/apache/bookkeeper/issues/221#issuecomment-321931809 sorry I typed the wrong issue id at #437. revert the labels and milestone. --

[GitHub] sijie closed pull request #437: Issue-431 Issue-221: merge scripts should mark milestone when merging pull requests

sijie closed pull request #437: Issue-431 Issue-221: merge scripts should mark milestone when merging pull requests URL: https://github.com/apache/bookkeeper/pull/437 This is an automated message from the Apache Git Service

[GitHub] sijie closed issue #431: merge scripts should mark milestone when merging pull requests

sijie closed issue #431: merge scripts should mark milestone when merging pull requests URL: https://github.com/apache/bookkeeper/issues/431 This is an automated message from the Apache Git Service. To respond to the messag

Re: Bug releases on Github

Okay. Let's try this to see if it help us. I am going to merge https://github.com/apache/bookkeeper/pull/437 so committers can start use it on merging pull requests. Please provide any feedback on this tool. We can together improve the tool. - Sijie On Fri, Aug 11, 2017 at 4:55 AM, Enrico Olive

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

sijie commented on a change in pull request #305: Issue 305: New Release Guide URL: https://github.com/apache/bookkeeper/pull/305#discussion_r132793031 ## File path: site/community/release_guide.md ## @@ -0,0 +1,475 @@ +# Apache BookKeeper Release Guide + +* TOC +{:toc} + +

Re: BP-12: Improve documentation

/cc (distributedlog-dev@) Thank you Enrico and Jia. I created a master issue for BP-12 : https://github.com/apache/bookkeeper/issues/439 for tracking all the efforts on improving documentation. I'd also like to call for volunteers to improve the documentation. You can check #439

[GitHub] sijie opened a new issue #439: BP-12 - Improve documentation

sijie opened a new issue #439: BP-12 - Improve documentation URL: https://github.com/apache/bookkeeper/issues/439 Created a master issue for [BP-12](https://cwiki.apache.org/confluence/display/BOOKKEEPER/BP-12+-+Improve+documentation) > How does it work? > > If you are interest

[GitHub] sijie closed issue #318: Documentation Improvements

sijie closed issue #318: Documentation Improvements URL: https://github.com/apache/bookkeeper/issues/318 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the U

[GitHub] sijie commented on issue #318: Documentation Improvements

sijie commented on issue #318: Documentation Improvements URL: https://github.com/apache/bookkeeper/issues/318#issuecomment-321924306 This issue was for the new website. all the sub-tasks have been completed. close it. This

Re: [DISCUSS] move github notifications to other mailing list

okay. if there is no complaints for sending the notifications of 'jenkins', 'jira' and 'git' to issues@ mailing list by end of this week, I will create an INFRA ticket for that. - Sijie On Fri, Aug 11, 2017 at 12:32 AM, Enrico Olivelli wrote: > Il ven 11 ago 2017, 02:07 Jia Zhai ha scritto: >

[GitHub] sijie commented on issue #438: Issue 435: Build javadoc for releases

sijie commented on issue #438: Issue 435: Build javadoc for releases URL: https://github.com/apache/bookkeeper/pull/438#issuecomment-321921080 this is the staging view: https://sijie.github.io/bookkeeper-staging-site/docs/4.5.0/overview/overview/ --

[GitHub] sijie opened a new pull request #438: Issue 435: Build javadoc for releases

sijie opened a new pull request #438: Issue 435: Build javadoc for releases URL: https://github.com/apache/bookkeeper/pull/438 Descriptions of the changes in this PR: - add javadoc links on sidebar and overview pages (try to promote this link for users to find the link easier) - u

[GitHub] sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321904168 @zhaijack @caiok @eolivelli based on the response on https://issues.apache.org/jira/browse/INFRA-14756, Dockerhub is not the official channel f

[GitHub] sijie commented on a change in pull request #305: Issue 305: New Release Guide

sijie commented on a change in pull request #305: Issue 305: New Release Guide URL: https://github.com/apache/bookkeeper/pull/305#discussion_r132767603 ## File path: site/community/release_guide.md ## @@ -0,0 +1,475 @@ +# Apache BookKeeper Release Guide + +* TOC +{:toc} + +

Re: [ANNOUNCE] Apache BookKeeper 4.5.0 released

Thank you Sebb! These are good questions and suggestions. We were following a template we used before. We will try to improve the template to add more descriptions and also more info on subsequent releases. - Sijie On Fri, Aug 11, 2017 at 11:47 AM, sebb wrote: > What is the project about? Why s

Re: [ANNOUNCE] Apache BookKeeper 4.5.0 released

What is the project about? Why should I be interested in it? [rhetorical questions] The Announce emails are sent to people not on the developer or user lists. Most will have no idea what the project is about. So the e-mails should contain at least brief details of what the product does, and some

Re: Time Based Release for onwards releases.

Matteo, Thank you for your comments. Make sense to me. Will update the BP if there is no other suggestions. Sijie On Aug 11, 2017 9:33 AM, "Matteo Merli" wrote: I would suggest to do quarterly releases (eg: every 3 months), since that seems to me a good tradeoff ratio between planning and agil

Re: [ANNOUNCE] Apache BookKeeper 4.5.0 released

Congrats to everyone! Now we have a common baseline and a great future together! Enrico Il ven 11 ago 2017, 20:03 Venkateswara Rao Jujjuri ha scritto: > Thanks a lot Sijie for patiently walking me through the process. > Now I have real appreciation for the release mangers. ;) > > On Fri, Aug 11

Re: [ANNOUNCE] Apache BookKeeper 4.5.0 released

Thanks a lot Sijie for patiently walking me through the process. Now I have real appreciation for the release mangers. ;) On Fri, Aug 11, 2017 at 10:59 AM, Sijie Guo wrote: > Awesome! Well done! This is a great milestone to the bookkeeper community! > > Thanks JV for doing the release! Thanks ev

Re: [ANNOUNCE] Apache BookKeeper 4.5.0 released

Awesome! Well done! This is a great milestone to the bookkeeper community! Thanks JV for doing the release! Thanks everyone for making this happen. Sijie On Aug 11, 2017 9:56 AM, "JV Jujjuri" wrote: > The Apache BookKeeper team is proud to announce Apache BookKeeper version > 4.5.0. > > This i

[ANNOUNCE] Apache BookKeeper 4.5.0 released

The Apache BookKeeper team is proud to announce Apache BookKeeper version 4.5.0. This is the fifth release of BookKeeper as an Apache Top Level Project! The 4.5.0 release incorporates hundreds of new fixes, improvements, and features since previous major release, 4.4.0, which was released over a

Re: Time Based Release for onwards releases.

I would suggest to do quarterly releases (eg: every 3 months), since that seems to me a good tradeoff ratio between planning and agility of shipping new features/improvements. Matteo On Fri, Aug 11, 2017 at 4:36 AM Enrico Olivelli wrote: > Il ven 11 ago 2017, 13:10 Sijie Guo ha scritto: > > >

Build failed in Jenkins: bookkeeper-master #1849

See Changes: [sijie] release 4.5.0: update website [sijie] ISSUE #356: Release notes 4.5.0 [sijie] ISSUE #432: Add "Google Analytics" to the website [sijie] ISSUE #414: use a clone of baseconf in new ServerCo

Re: BookKeeper docker image is avaliable under apache now

Good, happy to finally see it in docker hub! Thank you all! On Fri, 2017-08-11 at 03:59 -0700, Sijie Guo wrote: Awesome, Francesco and Jia! Nice work! - Sijie On Fri, Aug 11, 2017 at 3:53 AM, Enrico Olivelli mailto:eolive...@gmail.com>> wrote: Great! Thank you all, expecially Jia and Franc

Re: Bug releases on Github

Thank you. Good idea I hope I will be able to use it soon Enrico Il ven 11 ago 2017, 13:45 Jia Zhai ha scritto: > Since it may not easy to change the permissions for contributor, This PR is > a good alternative to make it easy. Thanks a lot to make it happen. > > On Fri, Aug 11, 2017 at 7:07 P

Re: Bug releases on Github

Since it may not easy to change the permissions for contributor, This PR is a good alternative to make it easy. Thanks a lot to make it happen. On Fri, Aug 11, 2017 at 7:07 PM, Sijie Guo wrote: > I've played around github API and come up a change to the merge script. It > handles adding milesto

[GitHub] zhaijack commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

zhaijack commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321789728 Got it. Let's wait for the answer. This is an automated message from the Apa

Re: Time Based Release for onwards releases.

Il ven 11 ago 2017, 13:10 Sijie Guo ha scritto: > Folks, please take a look at this. We need to decide the schedule for > 4.6.0. > Maybe we can take 4.3 clients as compatible baseline for 4.6. What is the next step? Shiuld you call a vote ? Enrico > - Sijie > > On Mon, Aug 7, 2017 at 6:59 PM

Re: Time Based Release for onwards releases.

Folks, please take a look at this. We need to decide the schedule for 4.6.0. - Sijie On Mon, Aug 7, 2017 at 6:59 PM, Sijie Guo wrote: > Hi all, > > First thanks everyone who contributed to 4.5.0 in the past year, and > especially thanks JV for spending time doing the release. The first release

Re: Time Based Release for onwards releases.

On Thu, Aug 10, 2017 at 2:12 AM, Enrico Olivelli wrote: > Il gio 10 ago 2017, 10:09 Sijie Guo ha scritto: > > > yes, it is end-of-life. For example, currently we kept all the release > > versions since 2011? but I believe there is no one still running releases > > like 4.0.* and 4.1.*, even 4.2*

Re: Bug releases on Github

I've played around github API and come up a change to the merge script. It handles adding milestone, labels (area, type and release) when merging pull requests. If a change is cherry-pick to a branch for bug fixes, a bug fix release is required to add as well. this is the pull request - https://gi

Re: BookKeeper docker image is avaliable under apache now

Awesome, Francesco and Jia! Nice work! - Sijie On Fri, Aug 11, 2017 at 3:53 AM, Enrico Olivelli wrote: > Great! > Thank you all, expecially Jia and Francesco ! > > Enrico > > Il ven 11 ago 2017, 10:48 Jia Zhai ha scritto: > >> FYI. BookKeeper docker image is avaliable under apache now: >> htt

Re: BookKeeper docker image is avaliable under apache now

Great! Thank you all, expecially Jia and Francesco ! Enrico Il ven 11 ago 2017, 10:48 Jia Zhai ha scritto: > FYI. BookKeeper docker image is avaliable under apache now: > https://hub.docker.com/r/apache/bookkeeper/ > -- -- Enrico Olivelli

[GitHub] sijie opened a new pull request #437: Issue 431: merge scripts should mark milestone when merging pull requests

sijie opened a new pull request #437: Issue 431: merge scripts should mark milestone when merging pull requests URL: https://github.com/apache/bookkeeper/pull/437 Descriptions of the changes in this PR: improve merge script to do: - assign a milestone - add `area/` label

[GitHub] sijie closed pull request #424: Issue 414: use a clone of baseconf in new ServerConfiguration(baseConf)

sijie closed pull request #424: Issue 414: use a clone of baseconf in new ServerConfiguration(baseConf) URL: https://github.com/apache/bookkeeper/pull/424 This is an automated message from the Apache Git Service. To respond

[GitHub] sijie closed issue #414: Test failure in UpdateLedgerOpTest

sijie closed issue #414: Test failure in UpdateLedgerOpTest URL: https://github.com/apache/bookkeeper/issues/414 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and u

[GitHub] sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321776907 FYI. I also cherry-picked the docker changes to branch 4.5. once this merge, the docker change would be in branch 4.5. However, I'd like t

[GitHub] sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

sijie commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321774564 since docker files are added for 4.5.0, I don't think we need to support previous releases. let's keep things simpler to just support 4.5.0 and o

BookKeeper docker image is avaliable under apache now

FYI. BookKeeper docker image is avaliable under apache now: https://hub.docker.com/r/apache/bookkeeper/

[GitHub] eolivelli commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

eolivelli commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321759593 I think that as 4.5 bookie is fully compatible with 4.4 clients we can support only 4.5 onwards -

[GitHub] zhaijack commented on issue #436: Issue 418: bump docker to use bk - 4.5.0

zhaijack commented on issue #436: Issue 418: bump docker to use bk - 4.5.0 URL: https://github.com/apache/bookkeeper/pull/436#issuecomment-321759275 @caiok @eolivelli Thanks for your review. @caiok, Yes , it need cherry pick for 4.5.0, thanks for the reminder. I would like to do it after

Jenkins build is still unstable: bookkeeper-release-nightly-snapshot #12

See

[GitHub] sijie commented on issue #424: Issue 414: use a clone of baseconf in new ServerConfiguration(baseConf)

sijie commented on issue #424: Issue 414: use a clone of baseconf in new ServerConfiguration(baseConf) URL: https://github.com/apache/bookkeeper/pull/424#issuecomment-321750002 @zhaijack fyi - I am testing a merge script change on updating labels, milestone and assignee. don't worry about

Re: [DISCUSS] move github notifications to other mailing list

Il ven 11 ago 2017, 02:07 Jia Zhai ha scritto: > ``` > We can possibly move "jekins", "jira" and "git" related emails to a > separate mailing list like issues@. for the mention emails, you might just > create a filter rule to categorize them. > ``` > 👍 > This seems enough to me. > > > On Fri, Aug