Re: Major and Minor Release Management

2019-02-20 Thread Sijie Guo
On Thu, Feb 21, 2019 at 10:57 AM Dave Fisher wrote: > > > > On Feb 20, 2019, at 6:47 PM, Sijie Guo wrote: > > > > On Wed, Feb 20, 2019 at 9:12 PM Ivan Kelly wrote: > > > >>> Can anyone propose a change to current release management? Otherwise it > >> is > >>> not a scalable solution because not

Build failed in Jenkins: pulsar-website-build #561

2019-02-20 Thread Apache Jenkins Server
See Changes: [guosijie] Minor improvement of CmdNamespaces and add the missing subcommands in [guosijie] Refactored handling of zero-queue consumer into separate subclass [github] Link wwrapper with pytho li

Re??Re: Major and Minor Release Management

2019-02-20 Thread ????????
> On Feb 20, 2019, at 6:47 PM, Sijie Guo wrote: > > On Wed, Feb 20, 2019 at 9:12 PM Ivan Kelly wrote: > >>> Can anyone propose a change to current release management? Otherwise it >> is >>> not a scalable solution because not every committer knows how to handle >>> this situation clearly. >> >

Re: Major and Minor Release Management

2019-02-20 Thread Dave Fisher
> On Feb 20, 2019, at 6:47 PM, Sijie Guo wrote: > > On Wed, Feb 20, 2019 at 9:12 PM Ivan Kelly wrote: > >>> Can anyone propose a change to current release management? Otherwise it >> is >>> not a scalable solution because not every committer knows how to handle >>> this situation clearly. >>

Re: Major and Minor Release Management

2019-02-20 Thread Sijie Guo
On Wed, Feb 20, 2019 at 9:12 PM Ivan Kelly wrote: > > Can anyone propose a change to current release management? Otherwise it > is > > not a scalable solution because not every committer knows how to handle > > this situation clearly. > > I agree that not every committer knows this. > What has wo

Re: Major and Minor Release Management

2019-02-20 Thread Ivan Kelly
> Can anyone propose a change to current release management? Otherwise it is > not a scalable solution because not every committer knows how to handle > this situation clearly. I agree that not every committer knows this. What has worked well for me in the past is to have _every_ commit go to mast

Major and Minor Release Management

2019-02-20 Thread Sijie Guo
Hi all, Can we discuss the policy for major and minor release management? The current approach using milestone for tracking how a pull request is merged is a bit confusing. For example, I am seeing some issues labelled as 2.3.1 but the pull requests are created based on master. I don't know how I

Slack digest for #dev - 2019-02-20

2019-02-20 Thread Apache Pulsar Slack
2019-02-19 09:11:57 UTC - Ivan Kelly: bookieshell is a mess 2019-02-19 11:30:02 UTC - Sijie Guo: totally agree. it is one of my tasks for 4.10 to clean up bookieshell and replace it with bkctl 2019-02-20 03:22:50 UTC - Jianfeng Qiao: @Jianfeng Qiao has joined the channel