Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[James Page]

Hi Ihar

On Mon, 8 Aug 2016 at 10:37 Ihar Hrachyshka  wrote:
[...]

> Any update on re-tagging the mitaka release of networking-l2gw with the
> > correct semantic version?  I'm working on packaging updates for Debian
> > and Ubuntu, and don't really want to push in 2016.1.0, only to have to
> > then bump the epoch (versioning semantic in Debian for dealing with
> > changes in versioning that result in out of order versions) again once
> > the next semantically versioned release comes out.
> >
>
> (Hey, neutron release liaison here.)
>

Hey!


> I was thinking we will stick to the (unfortunate) versioning for the
> subproject for the time of Mitaka. But I am happy to switch versioning if
> it makes someone’s life easier. Though I would like to hear a confirmation
> on that from l2gw folks first. (I added some cores to CC.)
>

1.0.0 -> 2016.1.0 -> 3.0.0 is the trick here as 3.0.0 < 2016.1.0; its
possible but I'd rather avoid the epochs in packaging if possible (I might
just skip 2016.1.0 and use a 1.0.0+git snapshot version instead to avoid
that situation).

So I can be flexible, but I suspect that this versioning inconsistency will
cause other deployment types issues as well.


>
> > Also, what are networking-l2gw's plans for Newton?  I also manage the
> > packaging of vmware-nsx, which amongst other things, depends on
> > networking-l2gw so it would be nice to have a co-ordinated release of
> > networking-l2gw, vmware-nsx (and networking-sfc and tap-as-a-service -
> > but I'll start another thread on that).
>
> Note that neither vmware-nsx nor taas is part of neutron stadium, and as
> such are not managed by neutron-release team. You would need to coordinate
> with them separately.
>

OK - I missed they are not part of neutron stadium ([0]); I'll hookup with
those teams individually (already in contact with the vmware-nsx team
anyway).

There was a thread on SFC lately asking for Mitaka release. I guess we
> don’t have any stable branches so far for the subproject.


Yeah - started a different thread on that one.

Cheers

James

[0]
http://docs.openstack.org/developer/neutron/stadium/sub_projects.html#official-sub-project-list
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Ihar Hrachyshka]

James Page  wrote:


Hi Carl

On Thu, 19 May 2016 at 21:51 Carl Baldwin  wrote:
On Thu, May 19, 2016 at 7:09 AM, Doug Hellmann   
wrote:

> We have the same issue with version numbers regressing no matter when we
> cut the next release, so it's up to the team. It might be easier to deal
> with now while it's fresh in our minds.
>
> I would like to update the instructions that were followed to give
> better information about version numbers. Can someone point me to the
> documentation that was used for the release process?

Hi, they are here [1].  Built from here [2].

Carl

Any update on re-tagging the mitaka release of networking-l2gw with the  
correct semantic version?  I'm working on packaging updates for Debian  
and Ubuntu, and don't really want to push in 2016.1.0, only to have to  
then bump the epoch (versioning semantic in Debian for dealing with  
changes in versioning that result in out of order versions) again once  
the next semantically versioned release comes out.




(Hey, neutron release liaison here.)

I was thinking we will stick to the (unfortunate) versioning for the  
subproject for the time of Mitaka. But I am happy to switch versioning if  
it makes someone’s life easier. Though I would like to hear a confirmation  
on that from l2gw folks first. (I added some cores to CC.)


Also, what are networking-l2gw's plans for Newton?  I also manage the  
packaging of vmware-nsx, which amongst other things, depends on  
networking-l2gw so it would be nice to have a co-ordinated release of  
networking-l2gw, vmware-nsx (and networking-sfc and tap-as-a-service -  
but I'll start another thread on that).


Note that neither vmware-nsx nor taas is part of neutron stadium, and as  
such are not managed by neutron-release team. You would need to coordinate  
with them separately.


There was a thread on SFC lately asking for Mitaka release. I guess we  
don’t have any stable branches so far for the subproject.


Ihar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[James Page]

Hi Carl

On Thu, 19 May 2016 at 21:51 Carl Baldwin  wrote:

> On Thu, May 19, 2016 at 7:09 AM, Doug Hellmann 
> wrote:
> > We have the same issue with version numbers regressing no matter when we
> > cut the next release, so it's up to the team. It might be easier to deal
> > with now while it's fresh in our minds.
> >
> > I would like to update the instructions that were followed to give
> > better information about version numbers. Can someone point me to the
> > documentation that was used for the release process?
>
> Hi, they are here [1].  Built from here [2].
>
> Carl
>

Any update on re-tagging the mitaka release of networking-l2gw with the
correct semantic version?  I'm working on packaging updates for Debian and
Ubuntu, and don't really want to push in 2016.1.0, only to have to then
bump the epoch (versioning semantic in Debian for dealing with changes in
versioning that result in out of order versions) again once the next
semantically versioned release comes out.

Also, what are networking-l2gw's plans for Newton?  I also manage the
packaging of vmware-nsx, which amongst other things, depends on
networking-l2gw so it would be nice to have a co-ordinated release of
networking-l2gw, vmware-nsx (and networking-sfc and tap-as-a-service - but
I'll start another thread on that).

Cheers

James
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Carl Baldwin]

On Thu, May 19, 2016 at 7:09 AM, Doug Hellmann  wrote:
> We have the same issue with version numbers regressing no matter when we
> cut the next release, so it's up to the team. It might be easier to deal
> with now while it's fresh in our minds.
>
> I would like to update the instructions that were followed to give
> better information about version numbers. Can someone point me to the
> documentation that was used for the release process?

Hi, they are here [1].  Built from here [2].

Carl

[1] 
http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html
[2] 
https://github.com/openstack/neutron/blob/master/doc/source/stadium/sub_project_guidelines.rst

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Doug Hellmann]

Excerpts from Ihar Hrachyshka's message of 2016-05-19 10:21:48 +0200:
> 
> > On 18 May 2016, at 23:16, Doug Hellmann  wrote:
> > 
> > Excerpts from Armando M.'s message of 2016-05-17 14:34:22 -0700:
> >> On 17 May 2016 at 03:25, Ihar Hrachyshka  wrote:
> >> 
> >>> 
>  On 16 May 2016, at 21:16, Armando M.  wrote:
>  
>  
>  
>  On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
>  
> > On 11 May 2016, at 22:05, Sukhdev Kapur 
> >>> wrote:
> > 
> > 
> > Folks,
> > 
> > I am happy to announce that Mitaka release for L2 Gateway is released
> >>> and now available at https://pypi.python.org/pypi/networking-l2gw.
> > 
> > You can install it by using "pip install networking-l2gw"
> > 
> > This release has several enhancements and fixes for issues discovered
> >>> in liberty release.
>  
>  How do you release it? I think the way to release new deliverables as of
> >>> Newton dev cycle is thru openstack/releases repository, as documented in
> >>> https://review.openstack.org/#/c/308984/
>  
>  Have you pushed git tag manually?
>  
>  I can only see the stable branch, tags can only be pushed by the
> >>> neutron-release team.
> >>> 
> >>> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
> >>> 
> >> 
> >> Weren't we supposed to use semver?
> > 
> > Yes, all releases should be using semver now.
> 
> Do we want to release another Mitaka release using semver, or it’s ok to wait 
> till Newton for the subproject?
> 
> Ihar

We have the same issue with version numbers regressing no matter when we
cut the next release, so it's up to the team. It might be easier to deal
with now while it's fresh in our minds.

I would like to update the instructions that were followed to give
better information about version numbers. Can someone point me to the
documentation that was used for the release process?

Thanks,
Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Ihar Hrachyshka]

> On 18 May 2016, at 23:16, Doug Hellmann  wrote:
> 
> Excerpts from Armando M.'s message of 2016-05-17 14:34:22 -0700:
>> On 17 May 2016 at 03:25, Ihar Hrachyshka  wrote:
>> 
>>> 
 On 16 May 2016, at 21:16, Armando M.  wrote:
 
 
 
 On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
 
> On 11 May 2016, at 22:05, Sukhdev Kapur 
>>> wrote:
> 
> 
> Folks,
> 
> I am happy to announce that Mitaka release for L2 Gateway is released
>>> and now available at https://pypi.python.org/pypi/networking-l2gw.
> 
> You can install it by using "pip install networking-l2gw"
> 
> This release has several enhancements and fixes for issues discovered
>>> in liberty release.
 
 How do you release it? I think the way to release new deliverables as of
>>> Newton dev cycle is thru openstack/releases repository, as documented in
>>> https://review.openstack.org/#/c/308984/
 
 Have you pushed git tag manually?
 
 I can only see the stable branch, tags can only be pushed by the
>>> neutron-release team.
>>> 
>>> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
>>> 
>> 
>> Weren't we supposed to use semver?
> 
> Yes, all releases should be using semver now.

Do we want to release another Mitaka release using semver, or it’s ok to wait 
till Newton for the subproject?

Ihar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Doug Hellmann]

Excerpts from Armando M.'s message of 2016-05-17 14:34:22 -0700:
> On 17 May 2016 at 03:25, Ihar Hrachyshka  wrote:
> 
> >
> > > On 16 May 2016, at 21:16, Armando M.  wrote:
> > >
> > >
> > >
> > > On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
> > >
> > > > On 11 May 2016, at 22:05, Sukhdev Kapur 
> > wrote:
> > > >
> > > >
> > > > Folks,
> > > >
> > > > I am happy to announce that Mitaka release for L2 Gateway is released
> > and now available at https://pypi.python.org/pypi/networking-l2gw.
> > > >
> > > > You can install it by using "pip install networking-l2gw"
> > > >
> > > > This release has several enhancements and fixes for issues discovered
> > in liberty release.
> > >
> > > How do you release it? I think the way to release new deliverables as of
> > Newton dev cycle is thru openstack/releases repository, as documented in
> > https://review.openstack.org/#/c/308984/
> > >
> > > Have you pushed git tag manually?
> > >
> > > I can only see the stable branch, tags can only be pushed by the
> > neutron-release team.
> >
> > 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
> >
> 
> Weren't we supposed to use semver?

Yes, all releases should be using semver now.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Armando M.]

On 17 May 2016 at 03:25, Ihar Hrachyshka  wrote:

>
> > On 16 May 2016, at 21:16, Armando M.  wrote:
> >
> >
> >
> > On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
> >
> > > On 11 May 2016, at 22:05, Sukhdev Kapur 
> wrote:
> > >
> > >
> > > Folks,
> > >
> > > I am happy to announce that Mitaka release for L2 Gateway is released
> and now available at https://pypi.python.org/pypi/networking-l2gw.
> > >
> > > You can install it by using "pip install networking-l2gw"
> > >
> > > This release has several enhancements and fixes for issues discovered
> in liberty release.
> >
> > How do you release it? I think the way to release new deliverables as of
> Newton dev cycle is thru openstack/releases repository, as documented in
> https://review.openstack.org/#/c/308984/
> >
> > Have you pushed git tag manually?
> >
> > I can only see the stable branch, tags can only be pushed by the
> neutron-release team.
>
> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
>

Weren't we supposed to use semver?


>
> Git tag history suggests that Carl pushed it (manually I guess?) It seems
> that we release some independent deliverables thru openstack/releases, and
> some manually pushing tags into repos.
>
> I would love if we can consolidate all our releases to use a single
> automation mechanism (openstack/releases patches), independent of release
> model. For that, I would like to hear from release folks whether we are
> allowed to use openstack/releases repo for release:independent deliverables
> that are part of an official project (neutron).
>
> [Note that it would not mean we move the oversight burden for those
> deliverables onto release team; neutron-release folks would still need to
> approve them; it’s only about technicalities, not governance]
>
> The existence of the following git directory suggests that it’s supported:
>
> https://github.com/openstack/releases/tree/master/deliverables/_independent
>
> We already have some networking-* subprojects there, like
> networking-bgpvpn or networking-odl. I would love to see all new releases
> tracked there.
>
> >
> > Ihar
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Carl Baldwin]

tl;dr  Merge changes to process documentation before expecting them to
be followed!  :)

On Tue, May 17, 2016 at 4:25 AM, Ihar Hrachyshka  wrote:
> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
>
> Git tag history suggests that Carl pushed it (manually I guess?) It seems 
> that we release some independent deliverables thru openstack/releases, and 
> some manually pushing tags into repos.

Yes, I did this manually.  I wondered about new process because I've
seen the review [1] but it has not merged and so I did not attempt to
follow it.  Merging these things signals changes in process and keeps
things clear and consistent for everyone.

> I would love if we can consolidate all our releases to use a single 
> automation mechanism (openstack/releases patches), independent of release 
> model. For that, I would like to hear from release folks whether we are 
> allowed to use openstack/releases repo for release:independent deliverables 
> that are part of an official project (neutron).

This would be great!  We just need to merge the changes to the
process.  I will continue to follow the process documented here [3].
(I even asked for some stale pages to be removed so that we wouldn't
be confused [2]).

Carl

[1] https://review.openstack.org/#/c/308984
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-May/094698.html
[3] 
http://docs.openstack.org/developer/neutron/stadium/sub_project_guidelines.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Ihar Hrachyshka]

> On 17 May 2016, at 16:46, Doug Hellmann  wrote:
> 
> Excerpts from Ihar Hrachyshka's message of 2016-05-17 14:39:40 +0200:
>> 
>>> On 17 May 2016, at 14:27, Doug Hellmann  wrote:
>>> 
>>> Excerpts from Ihar Hrachyshka's message of 2016-05-17 12:25:55 +0200:
 
> On 16 May 2016, at 21:16, Armando M.  wrote:
> 
> 
> 
> On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
> 
>> On 11 May 2016, at 22:05, Sukhdev Kapur  wrote:
>> 
>> 
>> Folks,
>> 
>> I am happy to announce that Mitaka release for L2 Gateway is released 
>> and now available at https://pypi.python.org/pypi/networking-l2gw.
>> 
>> You can install it by using "pip install networking-l2gw"
>> 
>> This release has several enhancements and fixes for issues discovered in 
>> liberty release.
> 
> How do you release it? I think the way to release new deliverables as of 
> Newton dev cycle is thru openstack/releases repository, as documented in 
> https://review.openstack.org/#/c/308984/
> 
> Have you pushed git tag manually?
> 
> I can only see the stable branch, tags can only be pushed by the 
> neutron-release team.  
 
 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
 
 Git tag history suggests that Carl pushed it (manually I guess?) It seems 
 that we release some independent deliverables thru openstack/releases, and 
 some manually pushing tags into repos.
 
 I would love if we can consolidate all our releases to use a single 
 automation mechanism (openstack/releases patches), independent of release 
 model. For that, I would like to hear from release folks whether we are 
 allowed to use openstack/releases repo for release:independent 
 deliverables that are part of an official project (neutron).
>>> 
>>> We're working on it. This cycle we've expanded coverage of the releases
>>> repo to all official projects using cycle-based models.
>>> 
 
 [Note that it would not mean we move the oversight burden for those 
 deliverables onto release team; neutron-release folks would still need to 
 approve them; it’s only about technicalities, not governance]
 
 The existence of the following git directory suggests that it’s supported:
 
 https://github.com/openstack/releases/tree/master/deliverables/_independent
 
 We already have some networking-* subprojects there, like 
 networking-bgpvpn or networking-odl. I would love to see all new releases 
 tracked there.
>>> 
>>> Any official projects following the independent model may use the
>>> openstack/releases repository to record their releases after they
>>> are tagged.
>> 
>> You mean we should follow the steps:
>> - first, push git tag manually;
>> - then, propose openstack/releases patch describing the new tag?
> 
> Yes.
> 
>> 
>> If that’s the case, it was not exactly followed for some late neutron 
>> stadium releases, like: https://review.openstack.org/#/c/308962/
>> 
>> Actually, that later one created the tag in the repo for us. So what’s the 
>> reason to take the first step manually?
> 
> Creating the tags is still a manual step, even when you submit the
> request and the release team does it for you. We've said we would help a
> few teams who asked, but most teams should tag themselves before
> recording the results in the releases repo. I expect this to change
> after newton, when the automation work is done.

Oh, that’s great to know. I haven’t realized that it’s not automated yet, and 
that release folks expect tags to be created before openstack/releases patches 
are sent for release:independent. I assume it’s documented somewhere?..

Ihar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Doug Hellmann]

Excerpts from Ihar Hrachyshka's message of 2016-05-17 14:39:40 +0200:
> 
> > On 17 May 2016, at 14:27, Doug Hellmann  wrote:
> > 
> > Excerpts from Ihar Hrachyshka's message of 2016-05-17 12:25:55 +0200:
> >> 
> >>> On 16 May 2016, at 21:16, Armando M.  wrote:
> >>> 
> >>> 
> >>> 
> >>> On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
> >>> 
>  On 11 May 2016, at 22:05, Sukhdev Kapur  wrote:
>  
>  
>  Folks,
>  
>  I am happy to announce that Mitaka release for L2 Gateway is released 
>  and now available at https://pypi.python.org/pypi/networking-l2gw.
>  
>  You can install it by using "pip install networking-l2gw"
>  
>  This release has several enhancements and fixes for issues discovered in 
>  liberty release.
> >>> 
> >>> How do you release it? I think the way to release new deliverables as of 
> >>> Newton dev cycle is thru openstack/releases repository, as documented in 
> >>> https://review.openstack.org/#/c/308984/
> >>> 
> >>> Have you pushed git tag manually?
> >>> 
> >>> I can only see the stable branch, tags can only be pushed by the 
> >>> neutron-release team.  
> >> 
> >> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
> >> 
> >> Git tag history suggests that Carl pushed it (manually I guess?) It seems 
> >> that we release some independent deliverables thru openstack/releases, and 
> >> some manually pushing tags into repos.
> >> 
> >> I would love if we can consolidate all our releases to use a single 
> >> automation mechanism (openstack/releases patches), independent of release 
> >> model. For that, I would like to hear from release folks whether we are 
> >> allowed to use openstack/releases repo for release:independent 
> >> deliverables that are part of an official project (neutron).
> > 
> > We're working on it. This cycle we've expanded coverage of the releases
> > repo to all official projects using cycle-based models.
> > 
> >> 
> >> [Note that it would not mean we move the oversight burden for those 
> >> deliverables onto release team; neutron-release folks would still need to 
> >> approve them; it’s only about technicalities, not governance]
> >> 
> >> The existence of the following git directory suggests that it’s supported:
> >> 
> >> https://github.com/openstack/releases/tree/master/deliverables/_independent
> >> 
> >> We already have some networking-* subprojects there, like 
> >> networking-bgpvpn or networking-odl. I would love to see all new releases 
> >> tracked there.
> > 
> > Any official projects following the independent model may use the
> > openstack/releases repository to record their releases after they
> > are tagged.
> 
> You mean we should follow the steps:
> - first, push git tag manually;
> - then, propose openstack/releases patch describing the new tag?

Yes.

> 
> If that’s the case, it was not exactly followed for some late neutron stadium 
> releases, like: https://review.openstack.org/#/c/308962/
> 
> Actually, that later one created the tag in the repo for us. So what’s the 
> reason to take the first step manually?

Creating the tags is still a manual step, even when you submit the
request and the release team does it for you. We've said we would help a
few teams who asked, but most teams should tag themselves before
recording the results in the releases repo. I expect this to change
after newton, when the automation work is done.

Doug

> 
> Ihar

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Ihar Hrachyshka]

> On 17 May 2016, at 14:27, Doug Hellmann  wrote:
> 
> Excerpts from Ihar Hrachyshka's message of 2016-05-17 12:25:55 +0200:
>> 
>>> On 16 May 2016, at 21:16, Armando M.  wrote:
>>> 
>>> 
>>> 
>>> On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
>>> 
 On 11 May 2016, at 22:05, Sukhdev Kapur  wrote:
 
 
 Folks,
 
 I am happy to announce that Mitaka release for L2 Gateway is released and 
 now available at https://pypi.python.org/pypi/networking-l2gw.
 
 You can install it by using "pip install networking-l2gw"
 
 This release has several enhancements and fixes for issues discovered in 
 liberty release.
>>> 
>>> How do you release it? I think the way to release new deliverables as of 
>>> Newton dev cycle is thru openstack/releases repository, as documented in 
>>> https://review.openstack.org/#/c/308984/
>>> 
>>> Have you pushed git tag manually?
>>> 
>>> I can only see the stable branch, tags can only be pushed by the 
>>> neutron-release team.  
>> 
>> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
>> 
>> Git tag history suggests that Carl pushed it (manually I guess?) It seems 
>> that we release some independent deliverables thru openstack/releases, and 
>> some manually pushing tags into repos.
>> 
>> I would love if we can consolidate all our releases to use a single 
>> automation mechanism (openstack/releases patches), independent of release 
>> model. For that, I would like to hear from release folks whether we are 
>> allowed to use openstack/releases repo for release:independent deliverables 
>> that are part of an official project (neutron).
> 
> We're working on it. This cycle we've expanded coverage of the releases
> repo to all official projects using cycle-based models.
> 
>> 
>> [Note that it would not mean we move the oversight burden for those 
>> deliverables onto release team; neutron-release folks would still need to 
>> approve them; it’s only about technicalities, not governance]
>> 
>> The existence of the following git directory suggests that it’s supported:
>> 
>> https://github.com/openstack/releases/tree/master/deliverables/_independent
>> 
>> We already have some networking-* subprojects there, like networking-bgpvpn 
>> or networking-odl. I would love to see all new releases tracked there.
> 
> Any official projects following the independent model may use the
> openstack/releases repository to record their releases after they
> are tagged.

You mean we should follow the steps:
- first, push git tag manually;
- then, propose openstack/releases patch describing the new tag?

If that’s the case, it was not exactly followed for some late neutron stadium 
releases, like: https://review.openstack.org/#/c/308962/

Actually, that later one created the tag in the repo for us. So what’s the 
reason to take the first step manually?

Ihar
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Doug Hellmann]

Excerpts from Ihar Hrachyshka's message of 2016-05-17 12:25:55 +0200:
> 
> > On 16 May 2016, at 21:16, Armando M.  wrote:
> > 
> > 
> > 
> > On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
> > 
> > > On 11 May 2016, at 22:05, Sukhdev Kapur  wrote:
> > >
> > >
> > > Folks,
> > >
> > > I am happy to announce that Mitaka release for L2 Gateway is released and 
> > > now available at https://pypi.python.org/pypi/networking-l2gw.
> > >
> > > You can install it by using "pip install networking-l2gw"
> > >
> > > This release has several enhancements and fixes for issues discovered in 
> > > liberty release.
> > 
> > How do you release it? I think the way to release new deliverables as of 
> > Newton dev cycle is thru openstack/releases repository, as documented in 
> > https://review.openstack.org/#/c/308984/
> > 
> > Have you pushed git tag manually?
> > 
> > I can only see the stable branch, tags can only be pushed by the 
> > neutron-release team.  
> 
> 2016.1.0 tag is in the repo, and is part of stable/mitaka branch.
> 
> Git tag history suggests that Carl pushed it (manually I guess?) It seems 
> that we release some independent deliverables thru openstack/releases, and 
> some manually pushing tags into repos.
> 
> I would love if we can consolidate all our releases to use a single 
> automation mechanism (openstack/releases patches), independent of release 
> model. For that, I would like to hear from release folks whether we are 
> allowed to use openstack/releases repo for release:independent deliverables 
> that are part of an official project (neutron).

We're working on it. This cycle we've expanded coverage of the releases
repo to all official projects using cycle-based models.

> 
> [Note that it would not mean we move the oversight burden for those 
> deliverables onto release team; neutron-release folks would still need to 
> approve them; it’s only about technicalities, not governance]
> 
> The existence of the following git directory suggests that it’s supported:
> 
> https://github.com/openstack/releases/tree/master/deliverables/_independent
> 
> We already have some networking-* subprojects there, like networking-bgpvpn 
> or networking-odl. I would love to see all new releases tracked there.

Any official projects following the independent model may use the
openstack/releases repository to record their releases after they
are tagged.

Doug

> 
> > 
> > Ihar
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [release] Re: [Neutron][L2GW] Mitaka release of L2 Gateway now available

[Ihar Hrachyshka]

> On 16 May 2016, at 21:16, Armando M.  wrote:
> 
> 
> 
> On 16 May 2016 at 05:15, Ihar Hrachyshka  wrote:
> 
> > On 11 May 2016, at 22:05, Sukhdev Kapur  wrote:
> >
> >
> > Folks,
> >
> > I am happy to announce that Mitaka release for L2 Gateway is released and 
> > now available at https://pypi.python.org/pypi/networking-l2gw.
> >
> > You can install it by using "pip install networking-l2gw"
> >
> > This release has several enhancements and fixes for issues discovered in 
> > liberty release.
> 
> How do you release it? I think the way to release new deliverables as of 
> Newton dev cycle is thru openstack/releases repository, as documented in 
> https://review.openstack.org/#/c/308984/
> 
> Have you pushed git tag manually?
> 
> I can only see the stable branch, tags can only be pushed by the 
> neutron-release team.  

2016.1.0 tag is in the repo, and is part of stable/mitaka branch.

Git tag history suggests that Carl pushed it (manually I guess?) It seems that 
we release some independent deliverables thru openstack/releases, and some 
manually pushing tags into repos.

I would love if we can consolidate all our releases to use a single automation 
mechanism (openstack/releases patches), independent of release model. For that, 
I would like to hear from release folks whether we are allowed to use 
openstack/releases repo for release:independent deliverables that are part of 
an official project (neutron).

[Note that it would not mean we move the oversight burden for those 
deliverables onto release team; neutron-release folks would still need to 
approve them; it’s only about technicalities, not governance]

The existence of the following git directory suggests that it’s supported:

https://github.com/openstack/releases/tree/master/deliverables/_independent

We already have some networking-* subprojects there, like networking-bgpvpn or 
networking-odl. I would love to see all new releases tracked there.

> 
> Ihar
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev