settingsLogin | Registersettings

[openstack-dev] OpenStack Havana End of Upstream Support Lifetime

0 votes

On 2014-09-30 01:38:29 +0000 (+0000), Jeremy Stanley wrote:
[...]

the tips of these branches have been tagged "havana-eol" in
preparation for branch deletion. The list of affected Git
repositories is as follows:

openstack-dev/devstack
openstack-dev/grenade
openstack/ceilometer
openstack/cinder
openstack/designate
openstack/glance
openstack/heat
openstack/horizon
openstack/keystone
openstack/neutron
openstack/nova
openstack/openstack-manuals
openstack/oslo-incubator
openstack/oslo.config
openstack/requirements
openstack/swift
openstack/tempest
openstack/trove

Just following up to note that I finally removed the stable/havana
branches of the above mentioned projects, in accordance with the EOL
announcement from a couple weeks ago.
--
Jeremy Stanley

asked Oct 9, 2014 in openstack-dev by Jeremy_Stanley (56,700 points)   3 5 7
retagged Jan 28, 2015 by admin

5 Responses

0 votes

On 10/09/2014 08:12 AM, Jeremy Stanley wrote:
On 2014-09-30 01:38:29 +0000 (+0000), Jeremy Stanley wrote:
[...]

the tips of these branches have been tagged "havana-eol" in
preparation for branch deletion. The list of affected Git
repositories is as follows:

 openstack-dev/devstack
 openstack-dev/grenade
 openstack/ceilometer
 openstack/cinder
 openstack/designate
 openstack/glance
 openstack/heat
 openstack/horizon
 openstack/keystone
 openstack/neutron
 openstack/nova
 openstack/openstack-manuals
 openstack/oslo-incubator
 openstack/oslo.config
 openstack/requirements
 openstack/swift
 openstack/tempest
 openstack/trove

Just following up to note that I finally removed the stable/havana
branches of the above mentioned projects, in accordance with the EOL
announcement from a couple weeks ago.

Just curious...why do we remove the stable branches for old releases?
Is the idea to force people onto new branches?

It seems like this just makes more work for people that are maintaining
older releases since it means they need to make sure to mirror things
before they go EOL.

Chris

responded Oct 9, 2014 by Chris_Friesen (20,420 points)   3 17 26
0 votes

On 10/9/14 1:31 PM, Chris Friesen wrote:
On 10/09/2014 08:12 AM, Jeremy Stanley wrote:

On 2014-09-30 01:38:29 +0000 (+0000), Jeremy Stanley wrote:
[...]

the tips of these branches have been tagged "havana-eol" in
preparation for branch deletion. The list of affected Git
repositories is as follows:

 openstack-dev/devstack
 openstack-dev/grenade
 openstack/ceilometer
 openstack/cinder
 openstack/designate
 openstack/glance
 openstack/heat
 openstack/horizon
 openstack/keystone
 openstack/neutron
 openstack/nova
 openstack/openstack-manuals
 openstack/oslo-incubator
 openstack/oslo.config
 openstack/requirements
 openstack/swift
 openstack/tempest
 openstack/trove

Just following up to note that I finally removed the stable/havana
branches of the above mentioned projects, in accordance with the EOL
announcement from a couple weeks ago.

Just curious...why do we remove the stable branches for old releases? Is the idea to force people onto new branches?

If I'm not mistaken; it appears the tag rename from "havana" -> "havana-eol" may be effecting the upgrade CI tests in recent commits (ex: [1]).

For example in real-db-upgradenovamysql_user001:th-mysql:
[snip]

2014-10-09 17:12:11,771 [output] Database is from Grizzly! Upgrade via Havana
2014-10-09 17:12:11,774 [output] error: branch 'stable/havana' not found.
2014-10-09 17:12:11,784 [output] Fetching origin
2014-10-09 17:12:16,634 [output] Switched to a new branch 'stable/havana'
2014-10-09 17:12:16,639 [output] fatal: ambiguous argument 'remotes/origin/stable/havana': unknown revision or path not in the working tree.

[/snip]

[1] https://review.openstack.org/#/c/126309/

responded Oct 9, 2014 by Boden_Russell (1,780 points)   2 5
0 votes

On 2014-10-09 11:31:37 -0600 (-0600), Chris Friesen wrote:
Just curious...why do we remove the stable branches for old
releases? Is the idea to force people onto new branches?

It's twofold. First, it's to indicate that the branch will be
getting no new patches ever. Second, it's because that's the only
good way to get Gerrit to refuse backports developers may try to
propose to the branch in error.

It seems like this just makes more work for people that are
maintaining older releases since it means they need to make sure
to mirror things before they go EOL.

No need to mirror them. The final commit to the stable/havana branch
is tagged havana-eol prior to deletion, as my announcement a couple
weeks ago mentioned. This preserves the commit history indefinitely,
so you can always create a local branch from that if you so desire.
--
Jeremy Stanley

responded Oct 9, 2014 by Jeremy_Stanley (56,700 points)   3 5 7
0 votes

On 2014-10-09 14:13:29 -0400 (-0400), Boden Russell wrote:
If I'm not mistaken; it appears the tag rename from "havana" ->
"havana-eol" may be effecting the upgrade CI tests in recent
commits (ex: [1]).

For example in real-db-upgradenovamysql_user001:th-mysql:
[...]

That's a third-party testing system reporting on those changes, not
run by the OpenStack project. I will however bring it to the
immediate attention of the operators at Rackspace maintaining the
"DB Datasets CI" (formerly "turbo-hipster") system. Thanks for the
heads up!
--
Jeremy Stanley

responded Oct 9, 2014 by Jeremy_Stanley (56,700 points)   3 5 7
0 votes

On 10/09/2014 02:39 PM, Jeremy Stanley wrote:
On 2014-10-09 11:31:37 -0600 (-0600), Chris Friesen wrote:

Just curious...why do we remove the stable branches for old
releases? Is the idea to force people onto new branches?

It's twofold. First, it's to indicate that the branch will be
getting no new patches ever. Second, it's because that's the only
good way to get Gerrit to refuse backports developers may try to
propose to the branch in error.

Okay, makes sense.

It seems like this just makes more work for people that are
maintaining older releases since it means they need to make sure
to mirror things before they go EOL.

No need to mirror them. The final commit to the stable/havana branch
is tagged havana-eol prior to deletion, as my announcement a couple
weeks ago mentioned. This preserves the commit history indefinitely,
so you can always create a local branch from that if you so desire.

Ah, okay. Apparently I skimmed too quickly and missed the part about it
being tagged still.

Thanks for the explanation.

Chris

responded Oct 9, 2014 by Chris_Friesen (20,420 points)   3 17 26
...