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
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-upgrade_nova_mysql_user001:th-mysql:
[...]
That's a third-par
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
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 + (+), Jeremy Stanley wrote:
> > [...]
> >> the tips of these branches have been tagged "havana-eol" in
> >> preparation for branch deletion. The list of affected Git
> >> re
On 10/09/2014 08:12 AM, Jeremy Stanley wrote:
On 2014-09-30 01:38:29 + (+), 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
open
On 2014-09-30 01:38:29 + (+), 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/ceilo
