Re: minor/bugfix release

[Sijie Guo]

Thank you Jai!

- Sijie

On Thu, Apr 19, 2018 at 11:42 AM, Jai Asher  wrote:

> +1 to 1.22.1 release - I think a bug fix (patch) release is a great idea
> especially if we have user-facing bugs. Since I was responsible for
> releasing 1.22, I don't mind taking up this task.
>
>
> On Thu, Apr 19, 2018 at 11:34 AM, Sijie Guo  wrote:
>
> > Hi all,
> >
> > I think there are a couple of bugs reported on 1.22.0 when users are
> using
> > it. Shall we consider doing a 1.22.1 release?
> >
> > - Sijie
> >
> > On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo  wrote:
> >
> > > Hi all,
> > >
> > > Currently pulsar release schedule is mainly on feature releases. Any
> idea
> > > on bugfix releases?
> > >
> > > E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1
> > > release with bug fixes?
> > >
> > > Thoughts?
> > >
> > > - Sijie
> > >
> > >
> >
>

Re: minor/bugfix release

[Matteo Merli]

> Since I was responsible for
releasing 1.22, I don't mind taking up this task.

Good, let's try to compile a list of commits with fixes that need to be
backported into 1.22.1 from master.

Jai, since the PRs can only have 1 milestone associated, we should use a
different way to mark them, perhaps with a github project.

On Thu, Apr 19, 2018 at 11:54 AM Sahaya Andrews  wrote:

> Agree.
>
> I can also take up the release task.
>
> On Thu, Apr 19, 2018 at 11:42 AM, Jai Asher  wrote:
> > +1 to 1.22.1 release - I think a bug fix (patch) release is a great idea
> > especially if we have user-facing bugs. Since I was responsible for
> > releasing 1.22, I don't mind taking up this task.
> >
> >
> > On Thu, Apr 19, 2018 at 11:34 AM, Sijie Guo  wrote:
> >
> >> Hi all,
> >>
> >> I think there are a couple of bugs reported on 1.22.0 when users are
> using
> >> it. Shall we consider doing a 1.22.1 release?
> >>
> >> - Sijie
> >>
> >> On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo  wrote:
> >>
> >> > Hi all,
> >> >
> >> > Currently pulsar release schedule is mainly on feature releases. Any
> idea
> >> > on bugfix releases?
> >> >
> >> > E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1
> >> > release with bug fixes?
> >> >
> >> > Thoughts?
> >> >
> >> > - Sijie
> >> >
> >> >
> >>
>
-- 
Matteo Merli

Re: minor/bugfix release

[Sahaya Andrews]

Agree.

I can also take up the release task.

On Thu, Apr 19, 2018 at 11:42 AM, Jai Asher  wrote:
> +1 to 1.22.1 release - I think a bug fix (patch) release is a great idea
> especially if we have user-facing bugs. Since I was responsible for
> releasing 1.22, I don't mind taking up this task.
>
>
> On Thu, Apr 19, 2018 at 11:34 AM, Sijie Guo  wrote:
>
>> Hi all,
>>
>> I think there are a couple of bugs reported on 1.22.0 when users are using
>> it. Shall we consider doing a 1.22.1 release?
>>
>> - Sijie
>>
>> On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo  wrote:
>>
>> > Hi all,
>> >
>> > Currently pulsar release schedule is mainly on feature releases. Any idea
>> > on bugfix releases?
>> >
>> > E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1
>> > release with bug fixes?
>> >
>> > Thoughts?
>> >
>> > - Sijie
>> >
>> >
>>

Re: minor/bugfix release

[Joe F]

+1

On Thu, Apr 19, 2018 at 11:34 AM, Sijie Guo  wrote:

> Hi all,
>
> I think there are a couple of bugs reported on 1.22.0 when users are using
> it. Shall we consider doing a 1.22.1 release?
>
> - Sijie
>
> On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo  wrote:
>
> > Hi all,
> >
> > Currently pulsar release schedule is mainly on feature releases. Any idea
> > on bugfix releases?
> >
> > E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1
> > release with bug fixes?
> >
> > Thoughts?
> >
> > - Sijie
> >
> >
>

Re: minor/bugfix release

[Jai Asher]

+1 to 1.22.1 release - I think a bug fix (patch) release is a great idea
especially if we have user-facing bugs. Since I was responsible for
releasing 1.22, I don't mind taking up this task.


On Thu, Apr 19, 2018 at 11:34 AM, Sijie Guo  wrote:

> Hi all,
>
> I think there are a couple of bugs reported on 1.22.0 when users are using
> it. Shall we consider doing a 1.22.1 release?
>
> - Sijie
>
> On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo  wrote:
>
> > Hi all,
> >
> > Currently pulsar release schedule is mainly on feature releases. Any idea
> > on bugfix releases?
> >
> > E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1
> > release with bug fixes?
> >
> > Thoughts?
> >
> > - Sijie
> >
> >
>

Re: minor/bugfix release

[Sijie Guo]

Hi all,

I think there are a couple of bugs reported on 1.22.0 when users are using
it. Shall we consider doing a 1.22.1 release?

- Sijie

On Wed, Apr 18, 2018 at 2:54 PM, Sijie Guo  wrote:

> Hi all,
>
> Currently pulsar release schedule is mainly on feature releases. Any idea
> on bugfix releases?
>
> E.g. If there are bugs on 1.22.0, shall we consider releasing 1.22.1
> release with bug fixes?
>
> Thoughts?
>
> - Sijie
>
>

Re: Plan for Pulsar 2.0 release

[Ivan Kelly]

On Thu, Apr 19, 2018 at 10:07 AM, Dave Fisher  wrote:
> Is it possible to have 2.0.0alpha on a Maven Central release?>

Zookeeper do it all the time.
http://search.maven.org/#artifactdetails%7Corg.apache.zookeeper%7Czookeeper%7C3.5.3-beta%7Cpom

-Ivan

Re: Plan for Pulsar 2.0 release

[Dave Fisher]

Is it possible to have 2.0.0alpha on a Maven Central release?

Sent from my iPhone

> On Apr 19, 2018, at 9:12 AM, Ivan Kelly  wrote:
> 
> Why not call it 2.0.0Alpha1, or 2.0.0Beta1? Calling it RC will be
> confusing for people who haven't read this conversation. The only
> problem with alpha or beta is that you won't get a 2.0.0 release in
> the end, but a 2.0.1. Many people don't trust '.0' releases anyhow
> though.
> 
> -Ivan
> 
>> On Thu, Apr 19, 2018 at 9:07 AM, Sahaya Andrews  wrote:
>> +1 from me as well.
>> 
>>> On Wed, Apr 18, 2018 at 5:10 PM, Nozomi Kurihara  
>>> wrote:
>>> + 1 for releasing RC version early
>>> 
>>> 
>>> 
>>> 差出人: Jia Zhai 
>>> 送信日時: 2018年4月19日 4:24
>>> 宛先: dev@pulsar.incubator.apache.org
>>> 件名: Re: Plan for Pulsar 2.0 release
>>> 
>>> +1
>>> 
 On Tue, Apr 17, 2018 at 2:25 PM, Jai Asher  wrote:
 
 +1 for releasing the RC early
 
> On Mon, Apr 16, 2018 at 6:52 PM Sijie Guo  wrote:
> 
> +1 for releasing an RC version prior to an official release.
> 
>> On Fri, Apr 13, 2018 at 9:27 AM, Matteo Merli  wrote:
>> 
>> Hi everyone,
>> 
>> I think we are approaching the completion of most major items that were
>> scheduled for 2.0 release.
>> 
>> Since there is a big number of items that went in, like for example:
>> * Migrating BookKeeper from Yahoo branch based on 4.3 to main Apache
 4.7
>> * Schema
>> * Topic Compaction
>> * Functions
>> * Client API refactorings
>> 
>> I would suggest to have a "2.0.0-RC1" release, still officially
 released
>> with regular process, so that we'll have a chance to iron out any bugs,
>> tools or packaging issue before marking 2.0 as "stable".
>> 
>> My idea is use next week to finish up all the pending tasks and
>> documentation changes and kickoff the release process for 2.0.0-rc1 in
> the
>> week after.
>> 
>> Any thoughts with respect to this?
>> 
>> Matteo
>> --
>> Matteo Merli
>> 
>> 
> 
 

Re: Plan for Pulsar 2.0 release

[Ivan Kelly]

Why not call it 2.0.0Alpha1, or 2.0.0Beta1? Calling it RC will be
confusing for people who haven't read this conversation. The only
problem with alpha or beta is that you won't get a 2.0.0 release in
the end, but a 2.0.1. Many people don't trust '.0' releases anyhow
though.

-Ivan

On Thu, Apr 19, 2018 at 9:07 AM, Sahaya Andrews  wrote:
> +1 from me as well.
>
> On Wed, Apr 18, 2018 at 5:10 PM, Nozomi Kurihara  
> wrote:
>> + 1 for releasing RC version early
>>
>>
>> 
>> 差出人: Jia Zhai 
>> 送信日時: 2018年4月19日 4:24
>> 宛先: dev@pulsar.incubator.apache.org
>> 件名: Re: Plan for Pulsar 2.0 release
>>
>> +1
>>
>> On Tue, Apr 17, 2018 at 2:25 PM, Jai Asher  wrote:
>>
>>> +1 for releasing the RC early
>>>
>>> On Mon, Apr 16, 2018 at 6:52 PM Sijie Guo  wrote:
>>>
>>> > +1 for releasing an RC version prior to an official release.
>>> >
>>> > On Fri, Apr 13, 2018 at 9:27 AM, Matteo Merli  wrote:
>>> >
>>> > > Hi everyone,
>>> > >
>>> > > I think we are approaching the completion of most major items that were
>>> > > scheduled for 2.0 release.
>>> > >
>>> > > Since there is a big number of items that went in, like for example:
>>> > >  * Migrating BookKeeper from Yahoo branch based on 4.3 to main Apache
>>> 4.7
>>> > >  * Schema
>>> > >  * Topic Compaction
>>> > >  * Functions
>>> > >  * Client API refactorings
>>> > >
>>> > > I would suggest to have a "2.0.0-RC1" release, still officially
>>> released
>>> > > with regular process, so that we'll have a chance to iron out any bugs,
>>> > > tools or packaging issue before marking 2.0 as "stable".
>>> > >
>>> > > My idea is use next week to finish up all the pending tasks and
>>> > > documentation changes and kickoff the release process for 2.0.0-rc1 in
>>> > the
>>> > > week after.
>>> > >
>>> > > Any thoughts with respect to this?
>>> > >
>>> > > Matteo
>>> > > --
>>> > > Matteo Merli
>>> > > 
>>> > >
>>> >
>>>

Re: Plan for Pulsar 2.0 release

[Sahaya Andrews]

+1 from me as well.

On Wed, Apr 18, 2018 at 5:10 PM, Nozomi Kurihara  wrote:
> + 1 for releasing RC version early
>
>
> 
> 差出人: Jia Zhai 
> 送信日時: 2018年4月19日 4:24
> 宛先: dev@pulsar.incubator.apache.org
> 件名: Re: Plan for Pulsar 2.0 release
>
> +1
>
> On Tue, Apr 17, 2018 at 2:25 PM, Jai Asher  wrote:
>
>> +1 for releasing the RC early
>>
>> On Mon, Apr 16, 2018 at 6:52 PM Sijie Guo  wrote:
>>
>> > +1 for releasing an RC version prior to an official release.
>> >
>> > On Fri, Apr 13, 2018 at 9:27 AM, Matteo Merli  wrote:
>> >
>> > > Hi everyone,
>> > >
>> > > I think we are approaching the completion of most major items that were
>> > > scheduled for 2.0 release.
>> > >
>> > > Since there is a big number of items that went in, like for example:
>> > >  * Migrating BookKeeper from Yahoo branch based on 4.3 to main Apache
>> 4.7
>> > >  * Schema
>> > >  * Topic Compaction
>> > >  * Functions
>> > >  * Client API refactorings
>> > >
>> > > I would suggest to have a "2.0.0-RC1" release, still officially
>> released
>> > > with regular process, so that we'll have a chance to iron out any bugs,
>> > > tools or packaging issue before marking 2.0 as "stable".
>> > >
>> > > My idea is use next week to finish up all the pending tasks and
>> > > documentation changes and kickoff the release process for 2.0.0-rc1 in
>> > the
>> > > week after.
>> > >
>> > > Any thoughts with respect to this?
>> > >
>> > > Matteo
>> > > --
>> > > Matteo Merli
>> > > 
>> > >
>> >
>>

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

[Apache Jenkins Server]

See 

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H24 (ubuntu xenial) in workspace 

[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Done
java.io.IOException: Failed to mkdirs: 

at hudson.FilePath.mkdirs(FilePath.java:1170)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1200)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1724)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: 

at hudson.FilePath.mkdirs(FilePath.java:1170)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1200)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1724)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Retrying after 10 seconds
java.io.IOException: Failed to mkdirs: 

at hudson.FilePath.mkdirs(FilePath.java:1170)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1200)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)
at hudson.model.Run.execute(Run.java:1724)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)