You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zeppelin.apache.org by Fengdong Yu <fe...@everstring.com> on 2015/11/09 03:12:54 UTC
Branch-0.5.5 is weird
Hi,
All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is weird. branch name is 0.5.5, but the actually version is 0.5.6.
A common proper way is create a new branch for 0.5.6 based on the 0.5.5, then changed the version to 0.5.6 on the new branch.
Re: Branch-0.5.5 is weird
Posted by Fengdong Yu <fe...@everstring.com>.
Yes, that make sense. we should keep the branch pom version never changed after released.
> On Nov 9, 2015, at 12:31 PM, moon soo Lee <mo...@apache.org> wrote:
>
> It was intended to branch-0.5 take care all 0.5.x release with tag.
> Only reason branch-0.5.5 is created for 0.5.5 instead of using branch-0.5
> since we decided to release 0.5.5 from master after it diverged a lot.
>
> So, I expect from 0.6.x we use single branch, branch-0.6 for all 0.6.x
> release with tags.
>
> For branch-0.5.5, would it make sense to leave version name as
> 0.5.5-incubating-SNAPSHOT after release in the pom.xml files?
>
> Thanks,
> moon
>
> On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik <co...@apache.org> wrote:
>
>> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
>>>
>>> Hi,
>>>
>>> All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is
>>> weird. branch name is 0.5.5, but the actually version is 0.5.6.
>>>
>>> A common proper way is create a new branch for 0.5.6 based on the 0.5.5,
>>> then changed the version to 0.5.6 on the new branch.
>>
>> There're a few school of thoughts here:
>> - one, as you explained, where new branch is created for each release
>> - another, where the same branch is used for a series of the releases, say
>> 0.5.x and each new release is simply tagged.
>>
>> Current situation with 0.5.5 is neither, because 0.5.5 isn't released yet,
>> but
>> the branch version is already moved. Which might lead to all sorts of the
>> confusions if more release candidates are needed.
>>
>> Cos
>>
Re: Branch-0.5.5 is weird
Posted by Konstantin Boudnik <co...@apache.org>.
yes, b) shouldn't be used once the release is out. Snapshot are for development. Using them otherwise is confusing as hell, for sure.
--
Regards,
Cos
On November 9, 2015 5:23:46 AM PST, moon soo Lee <mo...@apache.org> wrote:
>I also think it's not a big problem having multiple release in a branch
>with tags. for example Spark project does that.
>
>About version number in pom.xml in branch-0.5.5 after 0.5.5 release,
> a) 0.5.5-incubating
> b) 0.5.5-incubating-SNAPSHOT
> c) 0.5.6-incubating-SNAPSHOT
>
>I think a) more make sense than b) while keeping SNAPSHOT version after
>release certain version could be also very confusing.
>
>Thanks,
>moon
>
>On Mon, Nov 9, 2015 at 8:46 PM Felix Cheung <fe...@hotmail.com>
>wrote:
>
>> I think it's fine to have multiple releases from a branch-0.5. We
>should
>> probably change the release version when we are ready to cut a new
>release
>> though.
>>
>>
>>
>> _____________________________
>> From: Corneau Damien <co...@gmail.com>
>> Sent: Sunday, November 8, 2015 9:05 PM
>> Subject: Re: Branch-0.5.5 is weird
>> To: <de...@zeppelin.incubator.apache.org>
>>
>>
>> That's what the tag is for
>>
>> On Mon, Nov 9, 2015 at 2:03 PM, Fengdong Yu
><fe...@everstring.com>
>> wrote:
>>
>> > One branch take care only one release. then create a new branch
>for
>> next
>> > release.
>> >
>> > Don’t make branch-0.5 to take care 0.5.x release. that’s not make
>> sense.
>> >
>> > because if I want to get 0.5.3 source code after 0.5.5 released.
>It’s
>> > very trouble to get it.
>> >
>> >
>> >
>> >
>> > > On Nov 9, 2015, at 12:31 PM, moon soo Lee <mo...@apache.org>
>wrote:
>> > >
>> > > It was intended to branch-0.5 take care all 0.5.x release with
>tag.
>> > > Only reason branch-0.5.5 is created for 0.5.5 instead of using
>> branch-0.5
>> > > since we decided to release 0.5.5 from master after it diverged
>a lot.
>> > >
>> > > So, I expect from 0.6.x we use single branch, branch-0.6 for all
>0.6.x
>> > > release with tags.
>> > >
>> > > For branch-0.5.5, would it make sense to leave version name as
>> > > 0.5.5-incubating-SNAPSHOT after release in the pom.xml files?
>> > >
>> > > Thanks,
>> > > moon
>> > >
>> > > On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik
><co...@apache.org>
>> > wrote:
>> > >
>> > >> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
>> > >>>
>> > >>> Hi,
>> > >>>
>> > >>> All pom.xml under Branch-0.5.5 were changed version to 0.5.6,
>which
>> is
>> > >>> weird. branch name is 0.5.5, but the actually version is
>0.5.6.
>> > >>>
>> > >>> A common proper way is create a new branch for 0.5.6 based on
>the
>> > 0.5.5,
>> > >>> then changed the version to 0.5.6 on the new branch.
>> > >>
>> > >> There're a few school of thoughts here:
>> > >> - one, as you explained, where new branch is created for each
>release
>> > >> - another, where the same branch is used for a series of the
>> releases,
>> > say
>> > >> 0.5.x and each new release is simply tagged.
>> > >>
>> > >> Current situation with 0.5.5 is neither, because 0.5.5 isn't
>released
>> > yet,
>> > >> but
>> > >> the branch version is already moved. Which might lead to all
>sorts of
>> > the
>> > >> confusions if more release candidates are needed.
>> > >>
>> > >> Cos
>> > >>
>> >
>> >
Re: Branch-0.5.5 is weird
Posted by moon soo Lee <mo...@apache.org>.
I also think it's not a big problem having multiple release in a branch
with tags. for example Spark project does that.
About version number in pom.xml in branch-0.5.5 after 0.5.5 release,
a) 0.5.5-incubating
b) 0.5.5-incubating-SNAPSHOT
c) 0.5.6-incubating-SNAPSHOT
I think a) more make sense than b) while keeping SNAPSHOT version after
release certain version could be also very confusing.
Thanks,
moon
On Mon, Nov 9, 2015 at 8:46 PM Felix Cheung <fe...@hotmail.com>
wrote:
> I think it's fine to have multiple releases from a branch-0.5. We should
> probably change the release version when we are ready to cut a new release
> though.
>
>
>
> _____________________________
> From: Corneau Damien <co...@gmail.com>
> Sent: Sunday, November 8, 2015 9:05 PM
> Subject: Re: Branch-0.5.5 is weird
> To: <de...@zeppelin.incubator.apache.org>
>
>
> That's what the tag is for
>
> On Mon, Nov 9, 2015 at 2:03 PM, Fengdong Yu <fe...@everstring.com>
> wrote:
>
> > One branch take care only one release. then create a new branch for
> next
> > release.
> >
> > Don’t make branch-0.5 to take care 0.5.x release. that’s not make
> sense.
> >
> > because if I want to get 0.5.3 source code after 0.5.5 released. It’s
> > very trouble to get it.
> >
> >
> >
> >
> > > On Nov 9, 2015, at 12:31 PM, moon soo Lee <mo...@apache.org> wrote:
> > >
> > > It was intended to branch-0.5 take care all 0.5.x release with tag.
> > > Only reason branch-0.5.5 is created for 0.5.5 instead of using
> branch-0.5
> > > since we decided to release 0.5.5 from master after it diverged a lot.
> > >
> > > So, I expect from 0.6.x we use single branch, branch-0.6 for all 0.6.x
> > > release with tags.
> > >
> > > For branch-0.5.5, would it make sense to leave version name as
> > > 0.5.5-incubating-SNAPSHOT after release in the pom.xml files?
> > >
> > > Thanks,
> > > moon
> > >
> > > On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik <co...@apache.org>
> > wrote:
> > >
> > >> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
> > >>>
> > >>> Hi,
> > >>>
> > >>> All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which
> is
> > >>> weird. branch name is 0.5.5, but the actually version is 0.5.6.
> > >>>
> > >>> A common proper way is create a new branch for 0.5.6 based on the
> > 0.5.5,
> > >>> then changed the version to 0.5.6 on the new branch.
> > >>
> > >> There're a few school of thoughts here:
> > >> - one, as you explained, where new branch is created for each release
> > >> - another, where the same branch is used for a series of the
> releases,
> > say
> > >> 0.5.x and each new release is simply tagged.
> > >>
> > >> Current situation with 0.5.5 is neither, because 0.5.5 isn't released
> > yet,
> > >> but
> > >> the branch version is already moved. Which might lead to all sorts of
> > the
> > >> confusions if more release candidates are needed.
> > >>
> > >> Cos
> > >>
> >
> >
Re: Branch-0.5.5 is weird
Posted by Felix Cheung <fe...@hotmail.com>.
I think it's fine to have multiple releases from a branch-0.5. We should probably change the release version when we are ready to cut a new release though.
_____________________________
From: Corneau Damien <co...@gmail.com>
Sent: Sunday, November 8, 2015 9:05 PM
Subject: Re: Branch-0.5.5 is weird
To: <de...@zeppelin.incubator.apache.org>
That's what the tag is for
On Mon, Nov 9, 2015 at 2:03 PM, Fengdong Yu <fe...@everstring.com>
wrote:
> One branch take care only one release. then create a new branch for next
> release.
>
> Don’t make branch-0.5 to take care 0.5.x release. that’s not make sense.
>
> because if I want to get 0.5.3 source code after 0.5.5 released. It’s
> very trouble to get it.
>
>
>
>
> > On Nov 9, 2015, at 12:31 PM, moon soo Lee <mo...@apache.org> wrote:
> >
> > It was intended to branch-0.5 take care all 0.5.x release with tag.
> > Only reason branch-0.5.5 is created for 0.5.5 instead of using branch-0.5
> > since we decided to release 0.5.5 from master after it diverged a lot.
> >
> > So, I expect from 0.6.x we use single branch, branch-0.6 for all 0.6.x
> > release with tags.
> >
> > For branch-0.5.5, would it make sense to leave version name as
> > 0.5.5-incubating-SNAPSHOT after release in the pom.xml files?
> >
> > Thanks,
> > moon
> >
> > On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik <co...@apache.org>
> wrote:
> >
> >> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
> >>>
> >>> Hi,
> >>>
> >>> All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is
> >>> weird. branch name is 0.5.5, but the actually version is 0.5.6.
> >>>
> >>> A common proper way is create a new branch for 0.5.6 based on the
> 0.5.5,
> >>> then changed the version to 0.5.6 on the new branch.
> >>
> >> There're a few school of thoughts here:
> >> - one, as you explained, where new branch is created for each release
> >> - another, where the same branch is used for a series of the releases,
> say
> >> 0.5.x and each new release is simply tagged.
> >>
> >> Current situation with 0.5.5 is neither, because 0.5.5 isn't released
> yet,
> >> but
> >> the branch version is already moved. Which might lead to all sorts of
> the
> >> confusions if more release candidates are needed.
> >>
> >> Cos
> >>
>
>
Re: Branch-0.5.5 is weird
Posted by Corneau Damien <co...@gmail.com>.
That's what the tag is for
On Mon, Nov 9, 2015 at 2:03 PM, Fengdong Yu <fe...@everstring.com>
wrote:
> One branch take care only one release. then create a new branch for next
> release.
>
> Don’t make branch-0.5 to take care 0.5.x release. that’s not make sense.
>
> because if I want to get 0.5.3 source code after 0.5.5 released. It’s
> very trouble to get it.
>
>
>
>
> > On Nov 9, 2015, at 12:31 PM, moon soo Lee <mo...@apache.org> wrote:
> >
> > It was intended to branch-0.5 take care all 0.5.x release with tag.
> > Only reason branch-0.5.5 is created for 0.5.5 instead of using branch-0.5
> > since we decided to release 0.5.5 from master after it diverged a lot.
> >
> > So, I expect from 0.6.x we use single branch, branch-0.6 for all 0.6.x
> > release with tags.
> >
> > For branch-0.5.5, would it make sense to leave version name as
> > 0.5.5-incubating-SNAPSHOT after release in the pom.xml files?
> >
> > Thanks,
> > moon
> >
> > On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik <co...@apache.org>
> wrote:
> >
> >> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
> >>>
> >>> Hi,
> >>>
> >>> All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is
> >>> weird. branch name is 0.5.5, but the actually version is 0.5.6.
> >>>
> >>> A common proper way is create a new branch for 0.5.6 based on the
> 0.5.5,
> >>> then changed the version to 0.5.6 on the new branch.
> >>
> >> There're a few school of thoughts here:
> >> - one, as you explained, where new branch is created for each release
> >> - another, where the same branch is used for a series of the releases,
> say
> >> 0.5.x and each new release is simply tagged.
> >>
> >> Current situation with 0.5.5 is neither, because 0.5.5 isn't released
> yet,
> >> but
> >> the branch version is already moved. Which might lead to all sorts of
> the
> >> confusions if more release candidates are needed.
> >>
> >> Cos
> >>
>
>
Re: Branch-0.5.5 is weird
Posted by Fengdong Yu <fe...@everstring.com>.
One branch take care only one release. then create a new branch for next release.
Don’t make branch-0.5 to take care 0.5.x release. that’s not make sense.
because if I want to get 0.5.3 source code after 0.5.5 released. It’s very trouble to get it.
> On Nov 9, 2015, at 12:31 PM, moon soo Lee <mo...@apache.org> wrote:
>
> It was intended to branch-0.5 take care all 0.5.x release with tag.
> Only reason branch-0.5.5 is created for 0.5.5 instead of using branch-0.5
> since we decided to release 0.5.5 from master after it diverged a lot.
>
> So, I expect from 0.6.x we use single branch, branch-0.6 for all 0.6.x
> release with tags.
>
> For branch-0.5.5, would it make sense to leave version name as
> 0.5.5-incubating-SNAPSHOT after release in the pom.xml files?
>
> Thanks,
> moon
>
> On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik <co...@apache.org> wrote:
>
>> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
>>>
>>> Hi,
>>>
>>> All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is
>>> weird. branch name is 0.5.5, but the actually version is 0.5.6.
>>>
>>> A common proper way is create a new branch for 0.5.6 based on the 0.5.5,
>>> then changed the version to 0.5.6 on the new branch.
>>
>> There're a few school of thoughts here:
>> - one, as you explained, where new branch is created for each release
>> - another, where the same branch is used for a series of the releases, say
>> 0.5.x and each new release is simply tagged.
>>
>> Current situation with 0.5.5 is neither, because 0.5.5 isn't released yet,
>> but
>> the branch version is already moved. Which might lead to all sorts of the
>> confusions if more release candidates are needed.
>>
>> Cos
>>
Re: Branch-0.5.5 is weird
Posted by moon soo Lee <mo...@apache.org>.
It was intended to branch-0.5 take care all 0.5.x release with tag.
Only reason branch-0.5.5 is created for 0.5.5 instead of using branch-0.5
since we decided to release 0.5.5 from master after it diverged a lot.
So, I expect from 0.6.x we use single branch, branch-0.6 for all 0.6.x
release with tags.
For branch-0.5.5, would it make sense to leave version name as
0.5.5-incubating-SNAPSHOT after release in the pom.xml files?
Thanks,
moon
On Mon, Nov 9, 2015 at 11:17 AM Konstantin Boudnik <co...@apache.org> wrote:
> On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
> >
> > Hi,
> >
> > All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is
> > weird. branch name is 0.5.5, but the actually version is 0.5.6.
> >
> > A common proper way is create a new branch for 0.5.6 based on the 0.5.5,
> > then changed the version to 0.5.6 on the new branch.
>
> There're a few school of thoughts here:
> - one, as you explained, where new branch is created for each release
> - another, where the same branch is used for a series of the releases, say
> 0.5.x and each new release is simply tagged.
>
> Current situation with 0.5.5 is neither, because 0.5.5 isn't released yet,
> but
> the branch version is already moved. Which might lead to all sorts of the
> confusions if more release candidates are needed.
>
> Cos
>
Re: Branch-0.5.5 is weird
Posted by Konstantin Boudnik <co...@apache.org>.
On Mon, Nov 09, 2015 at 10:12AM, Fengdong Yu wrote:
>
> Hi,
>
> All pom.xml under Branch-0.5.5 were changed version to 0.5.6, which is
> weird. branch name is 0.5.5, but the actually version is 0.5.6.
>
> A common proper way is create a new branch for 0.5.6 based on the 0.5.5,
> then changed the version to 0.5.6 on the new branch.
There're a few school of thoughts here:
- one, as you explained, where new branch is created for each release
- another, where the same branch is used for a series of the releases, say
0.5.x and each new release is simply tagged.
Current situation with 0.5.5 is neither, because 0.5.5 isn't released yet, but
the branch version is already moved. Which might lead to all sorts of the
confusions if more release candidates are needed.
Cos