On 07/18/2017 08:21 AM, Andy McCrae wrote:
>
>
>
> The branches have now been retired, thanks to Joshua Hesketh!
>
>
> Thanks Josh, Andreas, Tony, and the rest of the Infra crew for sorting
> this out.
++ thanks all!
>
> Andy
>
>
>
>
>
>
> The branches have now been retired, thanks to Joshua Hesketh!
>
Thanks Josh, Andreas, Tony, and the rest of the Infra crew for sorting this
out.
Andy
__
OpenStack Development Mailing List (not for usage questions)
On 2017-07-17 19:09, Andreas Jaeger wrote:
> On 2017-07-17 15:51, Andy McCrae wrote:
>> We held back the openstack-ansible repo to allow us to point to the
>> mitaka-eol tag for the other role/project repos.
>> That's been done - I've created the mitaka-eol tag in the
>> openstack-ansible repo,
On Mon, Jul 17, 2017 at 07:09:13PM +0200, Andreas Jaeger wrote:
> On 2017-07-17 15:51, Andy McCrae wrote:
> > We held back the openstack-ansible repo to allow us to point to the
> > mitaka-eol tag for the other role/project repos.
> > That's been done - I've created the mitaka-eol tag in the
> >
On 2017-07-17 15:51, Andy McCrae wrote:
> We held back the openstack-ansible repo to allow us to point to the
> mitaka-eol tag for the other role/project repos.
> That's been done - I've created the mitaka-eol tag in the
> openstack-ansible repo, can we remove the stable/mitaka branch from
>
Hi Andreas,
OK, added. I'm waiting for packstack confirmation.
>
> The current list is now:
>
>
> openstack/sahara-extra stable/icehousePlease retire
> openstack/sahara-extra stable/mitaka Please retire
> openstack/packstack stable/kiloWaiting for
On Mon, Jul 10, 2017 at 11:33:51AM +, Gary Kotton wrote:
> Hi,
> Will this also be moving to eol -
> https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt?
We need to be very careful EOLing that repo (if at all) as project have
deep links to the
On 2017-07-10 13:33, Gary Kotton wrote:
> Hi,
> Will this also be moving to eol -
> https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt?
No, not planned yet,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH,
Hi,
Will this also be moving to eol -
https://github.com/openstack/requirements/blob/stable/mitaka/global-requirements.txt?
Thanks
Gary
On 7/10/17, 9:23 AM, "Andreas Jaeger" wrote:
On 2017-07-07 17:37, Doug Szumski wrote:
>
>> On 2017-07-05 12:13, Joshua Hesketh
On 2017-07-07 17:37, Doug Szumski wrote:
>
>> On 2017-07-05 12:13, Joshua Hesketh wrote:
>>> Hi all,
>>>
>>> Very sorry for the delay on processing this request. I have now EOL'd
>>> stable/mitaka branches for projects listed in [1].
>>>
>>> If there are any mistakes it should be possible to
> On 2017-07-05 12:13, Joshua Hesketh wrote:
> > Hi all,
> >
> > Very sorry for the delay on processing this request. I have now EOL'd
> > stable/mitaka branches for projects listed in [1].
> >
> > If there are any mistakes it should be possible to restore the branch
> > at the correct
On 2017-07-05 12:13, Joshua Hesketh wrote:
> Hi all,
>
> Very sorry for the delay on processing this request. I have now EOL'd
> stable/mitaka branches for projects listed in [1].
>
> If there are any mistakes it should be possible to restore the branch at
> the correct position. Similarly
On 2017-07-05 12:13, Joshua Hesketh wrote:
> Hi all,
>
> Very sorry for the delay on processing this request. I have now EOL'd
> stable/mitaka branches for projects listed in [1].
>
> If there are any mistakes it should be possible to restore the branch at
> the correct position. Similarly
Hi all,
Very sorry for the delay on processing this request. I have now EOL'd
stable/mitaka branches for projects listed in [1].
If there are any mistakes it should be possible to restore the branch at
the correct position. Similarly please let me know if there were any
projects that should have
On 2017-06-29 11:28:10 +1000 (+1000), Tony Breeds wrote:
[...]
> In the meantime we could look at adding permissions such that the Stable
> PTL (Well actually I guess eventually it'd be the same bot that does the
> release tagging) can push tags and abandon changes on all projects.
>
> Right now
On Wed, Jun 28, 2017 at 11:50:34PM +, Jeremy Stanley wrote:
> Indeed, that's a bummer. I hadn't noticed it until you pointed it
> out and assumed it had made it into the 2.13 series. Well, we're
> planning to look at logistics for a 2.14 upgrade soon once 2.13 is
> (hopefully!) in production,
On 2017-06-28 13:21:46 +1000 (+1000), Tony Breeds wrote:
> On Tue, Jun 27, 2017 at 08:59:27PM +, Jeremy Stanley wrote:
>
> > Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and
> > resume that much needed development effort.
>
> This looks to have landed in 2.14[1] :( I
On Wed, Jun 28, 2017 at 6:59 AM, Jeremy Stanley wrote:
> On 2017-06-17 01:20:28 +1000 (+1000), Joshua Hesketh wrote:
> [...]
> > I'm happy to help do this if you'd like. Otherwise the script I've
> > used for the last few retirements is here:
> >
On Tue, Jun 27, 2017 at 08:59:27PM +, Jeremy Stanley wrote:
> Fingers crossed that we'll be able to switch to Gerrit 2.13 soon and
> resume that much needed development effort.
This looks to have landed in 2.14[1] :( I don't know how hard it'd be
to backport to 2.13 or even if that's a
On 2017-06-17 01:20:28 +1000 (+1000), Joshua Hesketh wrote:
[...]
> I'm happy to help do this if you'd like. Otherwise the script I've
> used for the last few retirements is here:
> http://git.openstack.org/cgit/openstack-infra/release-tools/tree/eol_branch.sh
That would be really appreciated if
On Fri, Jun 16, 2017 at 02:14:59PM +, Jeremy Stanley wrote:
> On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote:
> [...]
> > It seeems a little odd to be following up so long after I first started
> > this thread but can someone on infra please process the EOLs as
> > described in
On Sat, Jun 17, 2017 at 12:14 AM, Jeremy Stanley wrote:
> On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote:
> [...]
> > It seeems a little odd to be following up so long after I first started
> > this thread but can someone on infra please process the EOLs as
> >
On 2017-06-16 15:12:36 +1000 (+1000), Tony Breeds wrote:
[...]
> It seeems a little odd to be following up so long after I first started
> this thread but can someone on infra please process the EOLs as
> described in [1].
[...]
I thought in prior discussions it had been determined that the
On Wed, Apr 12, 2017 at 04:47:25PM +1000, Tony Breeds wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
>
> I'm proposing to EOL all projects that meet
On Mon, Apr 24, 2017 at 10:43 PM, Emilien Macchi wrote:
> On Mon, Apr 17, 2017 at 1:03 PM, Emilien Macchi wrote:
>> On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds wrote:
>>> Hi all,
>>> I'm late in sending this announement, but
On Mon, Apr 17, 2017 at 1:03 PM, Emilien Macchi wrote:
> On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds wrote:
>> Hi all,
>> I'm late in sending this announement, but I'm glad to see several
>> projects
>> have already requested EOL releases to
On Mon, Apr 17, 2017 at 09:55:51AM -0400, Brian Rosmaita wrote:
> On 4/12/17 2:47 AM, Tony Breeds wrote:
> > Hi all,
> > I'm late in sending this announement, but I'm glad to see several
> > projects
> > have already requested EOL releases to make it trivial and obvious where to
> > apply the
On Wed, Apr 12, 2017 at 2:47 AM, Tony Breeds wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
>
> I'm proposing to EOL all
On 4/12/17 2:47 AM, Tony Breeds wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
>
> I'm proposing to EOL all projects ...
Hi Tony, just wanted to give
On Thu, Apr 13, 2017 at 04:58:12PM -0700, Samuel Cassiba wrote:
> Hi Tony,
>
> I’m not the PTL, but I asked in our channel. You can EOL Chef OpenStack as
> well. Thanks!
Cool.
I've added the Chef repos to the EOL list.
Yours Tony.
signature.asc
Description: PGP signature
On Thu, Apr 13, 2017 at 04:48:34PM -0700, Sumit Naiksatam wrote:
> Hi Tony, Kindly do not EOL openstack/group-based-policy, we are
> maintaining this branch.
Done.
Tony.
signature.asc
Description: PGP signature
__
Hi Tony,
I’m not the PTL, but I asked in our channel. You can EOL Chef OpenStack as
well. Thanks!
--
Best,
Samuel Cassiba
signature.asc
Description: Message signed with OpenPGP
__
OpenStack Development Mailing List (not
Hi Tony, Kindly do not EOL openstack/group-based-policy, we are
maintaining this branch.
Thanks,
~Sumit.
On Thu, Apr 13, 2017 at 4:40 PM, Tony Breeds wrote:
> On Thu, Apr 13, 2017 at 08:20:50AM -0600, Alex Schultz wrote:
>
>> I would not include puppet-midonet without
On Thu, Apr 13, 2017 at 03:55:56PM +0100, Andy McCrae wrote:
> Can the openstack-ansible repository be skipped until other repo's are
> EOL'd, please? The reason is that we'd like the mitaka-eol tag for OSA to
> point to the mitaka-eol tag of the appropriate upstream projects, in order
> for that
Hi Tony,
> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
> - A project is in list 1 and *really* *really* wants to opt *OUT* of
> EOLing and
> why. Note doing this will amost certainly reduce the testing coverage
> you
> have in the gate.
> - A project is in list 2
On Wed, Apr 12, 2017 at 6:21 PM, Tony Breeds wrote:
> On Wed, Apr 12, 2017 at 07:53:17AM -0600, Alex Schultz wrote:
>
>> Please EOL the Puppet OpenStack projects that have the stable/mitaka branch.
>
> Thanks Alex! I've added:
> openstack/puppet-aodh
>
On Wed, Apr 12, 2017 at 02:27:22PM +, gordon chung wrote:
> i imagine you can EOL python-aodhclient and ceilometermiddleware. thanks
Thanks I've added those repos/projects.
Yours Tony.
signature.asc
Description: PGP signature
On Wed, Apr 12, 2017 at 04:06:36PM +0200, Andreas Jaeger wrote:
> Please add openstack-manuals to the list for EOL,
Thanks Added!
Yours Tony.
signature.asc
Description: PGP signature
__
OpenStack Development Mailing List
On Wed, Apr 12, 2017 at 07:53:17AM -0600, Alex Schultz wrote:
> Please EOL the Puppet OpenStack projects that have the stable/mitaka branch.
Thanks Alex! I've added:
openstack/puppet-aodh
openstack/puppet-ceilometer
openstack/puppet-cinder
openstack/puppet-designate
openstack/puppet-glance
On 12/04/17 02:47 AM, Tony Breeds wrote:
> Please look over both lists by 2017-04-17 00:00 UTC and let me know if:
> - A project is in list 1 and *really* *really* wants to opt *OUT* of EOLing
> and
> why. Note doing this will amost certainly reduce the testing coverage you
> have in the
Please add openstack-manuals to the list for EOL,
Andreas
--
Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3
On Wed, Apr 12, 2017 at 12:47 AM, Tony Breeds wrote:
> Hi all,
> I'm late in sending this announement, but I'm glad to see several projects
> have already requested EOL releases to make it trivial and obvious where to
> apply the tag.
>
> I'm proposing to EOL all
Hi all,
I'm late in sending this announement, but I'm glad to see several projects
have already requested EOL releases to make it trivial and obvious where to
apply the tag.
I'm proposing to EOL all projects that meet one or more of the following
criteria:
- The project is
43 matches
Mail list logo