Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Cool, thanks Dougal! Renat Akhmerov @Nokia On 28 Jun 2017, 15:21 +0700, Dougal Matthews , wrote: > > On 23 June 2017 at 12:52, Thierry Carrez wrote: > > > Dougal Matthews wrote: > > > >>     We have been trying to break the requirement on mistral (from > > > >>     tripleo-common) but it is prov

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 23 June 2017 at 12:52, Thierry Carrez wrote: > Dougal Matthews wrote: > >> We have been trying to break the requirement on mistral (from > >> tripleo-common) but it is proving to be harder than expected. We are > >> really doing some nasty things, but I wont go into details here :-

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

We'll do that. Thanks Renat Akhmerov @Nokia 23 июня 2017 г., 18:54 +0700, Thierry Carrez , писал: > Dougal Matthews wrote: > > > We have been trying to break the requirement on mistral (from > > > tripleo-common) but it is proving to be harder than expected. We are > > > really doing some nasty

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Dougal Matthews wrote: >> We have been trying to break the requirement on mistral (from >> tripleo-common) but it is proving to be harder than expected. We are >> really doing some nasty things, but I wont go into details here :-) >> If anyone is interested, feel free to reach out.

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 22 June 2017 at 14:01, Dougal Matthews wrote: > > > On 22 June 2017 at 11:01, Thierry Carrez wrote: > >> Thierry Carrez wrote: >> > Renat Akhmerov wrote: >> >> We have a weekly meeting next Monday, will it be too late? >> > >> > Before Thursday EOD (when the Pike-2 deadline hits) should be OK

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 22 June 2017 at 11:01, Thierry Carrez wrote: > Thierry Carrez wrote: > > Renat Akhmerov wrote: > >> We have a weekly meeting next Monday, will it be too late? > > > > Before Thursday EOD (when the Pike-2 deadline hits) should be OK. > > If there was a decision, I missed it (and in the mean tim

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Thierry Carrez wrote: > Renat Akhmerov wrote: >> We have a weekly meeting next Monday, will it be too late? > > Before Thursday EOD (when the Pike-2 deadline hits) should be OK. If there was a decision, I missed it (and in the mean time Mistral published 5.0.0.0b2 for the Pike-2 milestone). Give

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On Fri, Jun 9, 2017 at 1:38 PM, Doug Hellmann wrote: > Excerpts from Alex Schultz's message of 2017-06-09 10:54:16 -0600: >> I ran into a case where I wanted to add python-tripleoclient to >> test-requirements for tripleo-heat-templates but it's not in the >> global requirements. In looking into a

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Excerpts from Alex Schultz's message of 2017-06-09 10:54:16 -0600: > I ran into a case where I wanted to add python-tripleoclient to > test-requirements for tripleo-heat-templates but it's not in the > global requirements. In looking into adding this, I noticed that > python-tripleoclient and tripl

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On Tue, May 30, 2017 at 3:08 PM, Emilien Macchi wrote: > On Tue, May 30, 2017 at 8:36 PM, Matthew Thode > wrote: >> We have a problem in requirements that projects that don't have the >> cycle-with-intermediary release model (most of the cycle-with-milestones >> model) don't get integrated with r

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 06/06/2017 03:21 AM, Dougal Matthews wrote: > > > On 31 May 2017 at 09:35, Renat Akhmerov > wrote: > > > On 31 May 2017, 15:08 +0700, Thierry Carrez >, wrote: >> >>> This has hit us with the mistral and tripleo proj

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 31 May 2017 at 09:35, Renat Akhmerov wrote: > > On 31 May 2017, 15:08 +0700, Thierry Carrez , > wrote: > > > This has hit us with the mistral and tripleo projects particularly > (tagged in the title). They disallow pbr-3.0.0 and in the case of > mistral sqlalchemy updates. > > [mistral] > mist

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Renat Akhmerov wrote: > We have a weekly meeting next Monday, will it be too late? Before Thursday EOD (when the Pike-2 deadline hits) should be OK. -- Thierry Carrez (ttx) __ OpenStack Development Mailing List (not for usa

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

We have a weekly meeting next Monday, will it be too late? Renat Akhmerov @Nokia On 1 Jun 2017, 20:10 +0700, Thierry Carrez , wrote: > Note that it's technically too late to change the release model > (milestone-1 is the deadline), but since that kills two birds with one > stone, I'd be willing t

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Note that it's technically too late to change the release model (milestone-1 is the deadline), but since that kills two birds with one stone, I'd be willing to grant mistral an exception (as long as it's done before milestone-2, which is next week). Renat Akhmerov wrote: > Thanks Thierry. > > To

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Thanks Thierry. To me it sounds like even a better release model for us. We can discuss it with a team at the next team meeting and make a decision. Renat Akhmerov @Nokia On 1 Jun 2017, 17:06 +0700, Thierry Carrez , wrote: > Renat Akhmerov wrote: > > On 31 May 2017, 15:08 +0700, Thierry Carrez

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Renat Akhmerov wrote: > On 31 May 2017, 15:08 +0700, Thierry Carrez , wrote: >>> [mistral] >>> mistral - blocking sqlalchemy - milestones >> >> I wonder why mistral is in requirements. Looks like tripleo-common is >> depending on it ? Could someone shine some light on this ? It might just >> mean m

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On Tue, May 30, 2017 at 11:11 PM, Matthew Thode wrote: > On 05/30/2017 04:08 PM, Emilien Macchi wrote: >> On Tue, May 30, 2017 at 8:36 PM, Matthew Thode >> wrote: >>> We have a problem in requirements that projects that don't have the >>> cycle-with-intermediary release model (most of the cycle-w

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

[horizon] django-openstack-auth - blocking django - intermediary https://review.openstack.org/#/c/469420 is up to release django_openstack_auth. Sorry for the delays. Rob __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 31 May 2017, 15:08 +0700, Thierry Carrez , wrote: > > > This has hit us with the mistral and tripleo projects particularly > > (tagged in the title). They disallow pbr-3.0.0 and in the case of > > mistral sqlalchemy updates. > > > > [mistral] > > mistral - blocking sqlalchemy - milestones > > I

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Matthew Thode wrote: > We have a problem in requirements that projects that don't have the > cycle-with-intermediary release model (most of the cycle-with-milestones > model) don't get integrated with requirements until the cycle is fully > done. This causes a few problems. > [...] Makes sense. R

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Excerpts from Matthew Thode's message of 2017-05-30 16:11:41 -0500: > On 05/30/2017 04:08 PM, Emilien Macchi wrote: > > On Tue, May 30, 2017 at 8:36 PM, Matthew Thode > > wrote: > >> We have a problem in requirements that projects that don't have the > >> cycle-with-intermediary release model (mos

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 05/30/2017 04:08 PM, Emilien Macchi wrote: > On Tue, May 30, 2017 at 8:36 PM, Matthew Thode > wrote: >> We have a problem in requirements that projects that don't have the >> cycle-with-intermediary release model (most of the cycle-with-milestones >> model) don't get integrated with requirement

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On Tue, May 30, 2017 at 8:36 PM, Matthew Thode wrote: > We have a problem in requirements that projects that don't have the > cycle-with-intermediary release model (most of the cycle-with-milestones > model) don't get integrated with requirements until the cycle is fully > done. This causes a few

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 05/30/2017 02:51 PM, Doug Hellmann wrote: > Excerpts from Matthew Thode's message of 2017-05-30 13:36:02 -0500: >> We have a problem in requirements that projects that don't have the >> cycle-with-intermediary release model (most of the cycle-with-milestones >> model) don't get integrated with r

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

Excerpts from Matthew Thode's message of 2017-05-30 13:36:02 -0500: > We have a problem in requirements that projects that don't have the > cycle-with-intermediary release model (most of the cycle-with-milestones > model) don't get integrated with requirements until the cycle is fully > done. This

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 05/30/2017 02:36 PM, Matthew Thode wrote: [nova] os-vif - blocking pbr - intermediary Sorry for the delay. We'll fix this up today. We'll need to cut a new release of os-traits too given a bug we ran into today... Thanks for keeping us honest! Best, -jay

[openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

We have a problem in requirements that projects that don't have the cycle-with-intermediary release model (most of the cycle-with-milestones model) don't get integrated with requirements until the cycle is fully done. This causes a few problems. * These projects don't produce a consumable release