Hey Jesse,
Sorry for the delay. I've gone ahead and removed icehouse, juno and kilo
branches creating tags in their places.
Cheers,
Josh
On Wed, Jul 6, 2016 at 3:27 AM, Jesse Pretorius <
jesse.pretor...@rackspace.co.uk> wrote:
> From: Joshua Hesketh
>
>
> I assume
From: Joshua Hesketh >
I assume you want to wait for the tag to merge before removing the branch?
The only tag job I can see for openstack-ansible* projects is the releasenotes
one. This should be harmless as it just generates the notes
On Fri, Jul 1, 2016 at 9:26 PM, Jesse Pretorius <
jesse.pretor...@rackspace.co.uk> wrote:
> Hi all,
>
> Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented
> we’ve requested a final tag [1]. Once that merges we are ready to have our
> kilo-eol tag implemented and the ‘kilo’
Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented we’ve
requested a final tag [1]. Once that merges we are ready to have our kilo-eol
tag implemented and the ‘kilo’ branch removed.
Whoops – I forget to add the link to the final Kilo tag request.
[1]
Hi all,
Now that OpenStack-Ansible has the final Swift kilo-eol tag implemented we’ve
requested a final tag [1]. Once that merges we are ready to have our kilo-eol
tag implemented and the ‘kilo’ branch removed.
Just to make life interesting, we still have leftover ‘juno’ and ‘icehouse’
On Sat, Jun 25, 2016 at 10:44 AM, Robert Collins
wrote:
> Removing the pbr branch should be fine - it was an exceptional thing
> to have that branch in the first place - pbr is consumed by releases
> only, and due to its place in the dependency graph is very very very
On Sat, Jun 25, 2016 at 4:20 AM, Sumit Naiksatam
wrote:
> Hi, I had earlier requested in this thread that the stable/kilo branch
> for the following repos be not deleted:
>
> > openstack/group-based-policy
> > openstack/group-based-policy-automation
> >
On Sat, Jun 25, 2016 at 4:20 AM, Sumit Naiksatam
wrote:
> Hi, I had earlier requested in this thread that the stable/kilo branch
> for the following repos be not deleted:
>
> > openstack/group-based-policy
> > openstack/group-based-policy-automation
> >
Removing the pbr branch should be fine - it was an exceptional thing
to have that branch in the first place - pbr is consumed by releases
only, and due to its place in the dependency graph is very very very
hard to pin or cap.
-Rob
On 25 June 2016 at 12:37, Tony Breeds
On Fri, Jun 24, 2016 at 04:36:03PM -0700, Sumit Naiksatam wrote:
> Hi Tony, Thanks for your response, and no worries! We can live with
> the kilo-eol tag, no need to try to delete it. And as you suggested,
> we can add a second eol tag when we actually EoL this branch.
>
> As regards reviving the
Hi Tony, Thanks for your response, and no worries! We can live with
the kilo-eol tag, no need to try to delete it. And as you suggested,
we can add a second eol tag when we actually EoL this branch.
As regards reviving the deleted branches, would a bug have to be
created somewhere to track this,
On Fri, Jun 24, 2016 at 11:20:12AM -0700, Sumit Naiksatam wrote:
> Hi, I had earlier requested in this thread that the stable/kilo branch
> for the following repos be not deleted:
>
> > openstack/group-based-policy
> > openstack/group-based-policy-automation
> > openstack/group-based-policy-ui
>
Hi, I had earlier requested in this thread that the stable/kilo branch
for the following repos be not deleted:
> openstack/group-based-policy
> openstack/group-based-policy-automation
> openstack/group-based-policy-ui
> openstack/python-group-based-policy-client
and the request was ack’ed by
On 06/24/2016 02:09 PM, Joshua Hesketh wrote:
Hi all,
I have completed removing stable/kilo branches from the projects listed
[0]*. There are now 'kilo-eol' tags in place at the sha's where the
branches were.
*There are a couple of exceptions. oslo-incubator was listed but is an
unmaintained
Hi all,
I have completed removing stable/kilo branches from the projects listed
[0]*. There are now 'kilo-eol' tags in place at the sha's where the
branches were.
*There are a couple of exceptions. oslo-incubator was listed but is an
unmaintained project so no further action was required. Tony
On 6/2/16 4:31 AM, Tony Breeds wrote:
> Any projects that will be EOL'd will need all open reviews abandoned before it
> can be processed.
openstack/vmware-nsx kilo patches have been abandoned in preparation for
the EOL.
Thanks
On Thu, Jun 09, 2016 at 02:16:10AM -0700, Sumit Naiksatam wrote:
> Hi Tony, The following repos should not be included in the EoL list since
> they will not be EoL'ed at this time:
> openstack/group-based-policy
> openstack/group-based-policy-automation
> openstack/group-based-policy-ui
>
On Thu, Jun 9, 2016 at 3:10 PM, Ihar Hrachyshka wrote:
>
>> On 10 Jun 2016, at 00:03, Sumit Naiksatam wrote:
>>
>> On Thu, Jun 9, 2016 at 2:26 AM, Ihar Hrachyshka wrote:
>>>
On 09 Jun 2016, at 11:16, Sumit Naiksatam
> On 10 Jun 2016, at 00:03, Sumit Naiksatam wrote:
>
> On Thu, Jun 9, 2016 at 2:26 AM, Ihar Hrachyshka wrote:
>>
>>> On 09 Jun 2016, at 11:16, Sumit Naiksatam wrote:
>>>
>>> Hi Tony, The following repos should not be
On Thu, Jun 9, 2016 at 2:26 AM, Ihar Hrachyshka wrote:
>
>> On 09 Jun 2016, at 11:16, Sumit Naiksatam wrote:
>>
>> Hi Tony, The following repos should not be included in the EoL list since
>> they will not be EoL'ed at this time:
>>
> On 09 Jun 2016, at 11:16, Sumit Naiksatam wrote:
>
> Hi Tony, The following repos should not be included in the EoL list since
> they will not be EoL'ed at this time:
> openstack/group-based-policy
> openstack/group-based-policy-automation
Hi Tony, The following repos should not be included in the EoL list since
they will not be EoL'ed at this time:
openstack/group-based-policy
openstack/group-based-policy-automation
openstack/group-based-policy-ui
openstack/python-group-based-policy-client
Thanks,
Sumit.
On Jun 9, 2016 12:16 AM,
On Fri, Jun 03, 2016 at 04:25:01PM +1000, Tony Breeds wrote:
> On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote:
> > Hi all,
> > In early May we tagged/EOL'd several (13) projects. We'd like to do a
> > final round for a more complete set. We looked for projects meet one or
> >
Regarding openstack/murano-apps, in this repo we use stable/kilo
branch not as a version of the apps, but rather than compatibility
version of the app. Applications which are published in this branch
are compatible with Murano from stable/kilo, given than we have a lag
between upstream release and
I’ve submitted a request to release all the unreleased code we still have
for murano repositories https://review.openstack.org/#/c/325359/ ; It would
be really great if we could get one final release before EOL’ing kilo in
murano, murano-dashboard, murano-agent and python-muranoclient, if that is
On Fri, Jun 03, 2016 at 03:05:36PM +0200, Alan Pevec wrote:
> > openstack/packstack BigTent
>
> Just to clarify, Packstack has not formally applied to BigTent yet, it
> has only been automatically migrated from stackforge to openstack
> namespace.
Okay
On Thu, Jun 2, 2016 at 7:32 PM, Tony Breeds wrote:
> On Thu, Jun 02, 2016 at 07:10:23PM -0400, Emilien Macchi wrote:
>
>> I think that all openstack/puppet-* projects that have stable/kilo can
>> be kilo-EOLed.
>> Let me know if it's ok and I'll abandon all open reviews.
> openstack/packstack BigTent
Just to clarify, Packstack has not formally applied to BigTent yet, it
has only been automatically migrated from stackforge to openstack
namespace.
But yes, please keep its kilo branch for now until we properly wrap it up.
On Fri, Jun 03, 2016 at 09:29:34AM +0200, Matthias Runge wrote:
> On 02/06/16 12:31, Tony Breeds wrote:
> > The list of 171 projects that match above is at [1]. There are
> > another 68
> I just abandoned open reviews for django_openstack_auth in kilo version.
Thanks.
Yours Tony.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/06/16 12:31, Tony Breeds wrote:
> Hi all, In early May we tagged/EOL'd several (13) projects. We'd
> like to do a final round for a more complete set. We looked for
> projects meet one or more of the following criteria: - The project
> is
On Thu, Jun 02, 2016 at 08:31:43PM +1000, Tony Breeds wrote:
> Hi all,
> In early May we tagged/EOL'd several (13) projects. We'd like to do a
> final round for a more complete set. We looked for projects meet one or more
> of the following criteria:
> - The project is
On Thu, Jun 02, 2016 at 08:41:40AM -0700, John Dickinson wrote:
> open swift/swiftclient patches to stable/kilo have been abandoned
Thanks John
Tony.
signature.asc
Description: PGP signature
__
OpenStack Development
On Thu, Jun 02, 2016 at 07:10:23PM -0400, Emilien Macchi wrote:
> I think that all openstack/puppet-* projects that have stable/kilo can
> be kilo-EOLed.
> Let me know if it's ok and I'll abandon all open reviews.
Totally fine with me.
I've added them. Feel free to abanond the reviews. Any
On Thu, Jun 02, 2016 at 12:38:15PM +0200, Ihar Hrachyshka wrote:
> I think all networking-* repos should EOL too, since they are plugins to
> neutron which is already EOL. I struggle to find a way that could maintain
> their gate without neutron.
Thanks I've added them.
Yours Tony.
On Thu, Jun 2, 2016 at 6:31 AM, Tony Breeds wrote:
> Hi all,
> In early May we tagged/EOL'd several (13) projects. We'd like to do a
> final round for a more complete set. We looked for projects meet one or more
> of the following criteria:
> - The project is
open swift/swiftclient patches to stable/kilo have been abandoned
--John
On 2 Jun 2016, at 4:45, Jesse Pretorius wrote:
> Hi Tony,
>
> OpenStack-Ansible is just waiting for the requirements repository and the
> swift repository kilo-eol tags. Once they're done we'd like to bump the
> SHA's
Hi Tony,
OpenStack-Ansible is just waiting for the requirements repository and the
swift repository kilo-eol tags. Once they're done we'd like to bump the
SHA's for our 'kilo' to the EOL tags of those two repositories, tag a
release, then do our own kilo-eol tag.
Thanks,
Jesse
IRC: odyssey4me
I think all networking-* repos should EOL too, since they are plugins to
neutron which is already EOL. I struggle to find a way that could maintain
their gate without neutron.
> On 02 Jun 2016, at 12:31, Tony Breeds wrote:
>
> Hi all,
>In early May we tagged/EOL'd
Hi all,
In early May we tagged/EOL'd several (13) projects. We'd like to do a
final round for a more complete set. We looked for projects meet one or more
of the following criteria:
- The project is openstack-dev/devstack, openstack-dev/grenade or
openstack/requirements
- The project has
39 matches
Mail list logo