Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[Sean McGinnis]

On Fri, Aug 18, 2017 at 07:00:08PM +, gordon chung wrote:
> apologies, I'm currently away on vacation (for a while)
> 
> we can merge the stable/pike patch as it seems there are others dependent on 
> it. I don't believe it affects us either way.
> 
> I don't see the auto patch that creates tag so I guess we need to do it via 
> releases project
> 
> --
> 
> gord

Correct, that is done via a patch proposed to the releases repo.

There's a little more instruction here:

http://lists.openstack.org/pipermail/openstack-dev/2017-August/121266.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[gordon chung]

apologies, I'm currently away on vacation (for a while)

we can merge the stable/pike patch as it seems there are others dependent on 
it. I don't believe it affects us either way.

I don't see the auto patch that creates tag so I guess we need to do it via 
releases project

--

gord




From: Sean McGinnis <sean.mcgin...@gmx.com>
Sent: Friday, August 18, 2017 4:31:44 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike 
branch outlook

> > >>
> > >> Can someone on the release team clarify this for us?
> > >
> > > That's correct the bit you're missing is cycle-with-intermediary
> doesn't
> > > have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels
> > > they have the code in shape for a release they'll tag that release and
> > > cut a stable/pike branch at the tag point.
> >

>
> that email explicitly says: "Deliverables following the
> cycle-with-intermediary model should also create their Pike release branch
> next week. That means potentially making a last Pike release, and in all
> cases posting the stable/pike branch creation request"
>
> And that wasn't done for ceilometer. So it needs to be done, right?
>

Yes, I just double checked, and there has not been a pike release yet for
ceilometer. That does need to be done soon.

Sean

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[Sean McGinnis]

> > >>
> > >> Can someone on the release team clarify this for us?
> > >
> > > That's correct the bit you're missing is cycle-with-intermediary
> doesn't
> > > have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels
> > > they have the code in shape for a release they'll tag that release and
> > > cut a stable/pike branch at the tag point.
> >

> 
> that email explicitly says: "Deliverables following the
> cycle-with-intermediary model should also create their Pike release branch
> next week. That means potentially making a last Pike release, and in all
> cases posting the stable/pike branch creation request"
> 
> And that wasn't done for ceilometer. So it needs to be done, right?
> 

Yes, I just double checked, and there has not been a pike release yet for
ceilometer. That does need to be done soon.

Sean

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[William M Edmonds]

Thierry Carrez <thie...@openstack.org> wrote on 08/17/2017 03:35:20 AM:
> From: Thierry Carrez <thie...@openstack.org>
> To: openstack-dev@lists.openstack.org
> Date: 08/17/2017 03:37 AM
> Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer
> stable/pike branch outlook
>
> Tony Breeds wrote:
> > On Wed, Aug 16, 2017 at 02:37:50PM -0400, William M Edmonds wrote:
> >>
> >> Julien Danjou <jul...@danjou.info> wrote on 08/16/2017 02:13:10 PM:
> >>> AFAIU it's impossible to cut a branch for our projects and release a
rc1
> >>> because of the release model we use. The release team does not allow
us
> >>> to do that. We need to release directly a stable version and cut a
> >>> branch.
> >>>
> >>> I guess we'll do that in a couple of week, at release time.
> >>
> >> That doesn't fit my understanding of cycle-with-intermediary, which is
the
> >> the ceilometer release model per [0]. As I read the release model
> >> definitions [1], cycle-with-intermediary means that you can have
> >> intermediate releases *as well*, but you still have to have a
cycle-ending
> >> release in line with the projects using the cycle-with-milestones
model.
> >>
> >> Can someone on the release team clarify this for us?
> >
> > That's correct the bit you're missing is cycle-with-intermediary
doesn't
> > have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels
> > they have the code in shape for a release they'll tag that release and
> > cut a stable/pike branch at the tag point.
>
> Exactly. As explained a couple weeks ago in the release countdown email
[1]:
>

that email explicitly says: "Deliverables following the
cycle-with-intermediary model should also create their Pike release branch
next week. That means potentially making a last Pike release, and in all
cases posting the stable/pike branch creation request"

And that wasn't done for ceilometer. So it needs to be done, right?

> > Deliverables following the cycle-with-intermediary model should also
> > create their Pike release branch next week. That means potentially
> > making a last Pike release, and in all cases posting the stable/pike
> > branch creation request:
> >
> > ...
> > branches:
> >   - location: YOUR.PIKE.VERSION
> > name: stable/pike
>
> [1]
>
http://lists.openstack.org/pipermail/openstack-dev/2017-August/120574.html
>
> --
> Thierry Carrez (ttx)
>
> [attachment "signature.asc" deleted by William M Edmonds/Raleigh/
> IBM]
>
__
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[Thierry Carrez]

Tony Breeds wrote:
> On Wed, Aug 16, 2017 at 02:37:50PM -0400, William M Edmonds wrote:
>>
>> Julien Danjou  wrote on 08/16/2017 02:13:10 PM:
>>> AFAIU it's impossible to cut a branch for our projects and release a rc1
>>> because of the release model we use. The release team does not allow us
>>> to do that. We need to release directly a stable version and cut a
>>> branch.
>>>
>>> I guess we'll do that in a couple of week, at release time.
>>
>> That doesn't fit my understanding of cycle-with-intermediary, which is the
>> the ceilometer release model per [0]. As I read the release model
>> definitions [1], cycle-with-intermediary means that you can have
>> intermediate releases *as well*, but you still have to have a cycle-ending
>> release in line with the projects using the cycle-with-milestones model.
>>
>> Can someone on the release team clarify this for us?
> 
> That's correct the bit you're missing is cycle-with-intermediary doesn't
> have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels
> they have the code in shape for a release they'll tag that release and
> cut a stable/pike branch at the tag point.

Exactly. As explained a couple weeks ago in the release countdown email[1]:

> Deliverables following the cycle-with-intermediary model should also
> create their Pike release branch next week. That means potentially
> making a last Pike release, and in all cases posting the stable/pike
> branch creation request:
> 
> ...
> branches:
>   - location: YOUR.PIKE.VERSION
> name: stable/pike

[1]
http://lists.openstack.org/pipermail/openstack-dev/2017-August/120574.html

-- 
Thierry Carrez (ttx)



signature.asc
Description: OpenPGP digital signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[Tony Breeds]

On Wed, Aug 16, 2017 at 02:37:50PM -0400, William M Edmonds wrote:
> 
> Julien Danjou <jul...@danjou.info> wrote on 08/16/2017 02:13:10 PM:
> > From: Julien Danjou <jul...@danjou.info>
> > To: "Eric S Berglund" <esber...@us.ibm.com>
> > Cc: openstack-dev@lists.openstack.org
> > Date: 08/16/2017 02:14 PM
> > Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer
> > stable/pike branch outlook
> >
> > On Wed, Aug 16 2017, Eric S Berglund wrote:
> >
> > Hi Eric,
> >
> > > Is there an outlook for cutting a pike branch for ceilometer?
> > > We currently can't run our 3rd party CI against pike without a pike
> > > release branch and are deciding whether it's worth the time to
> > > implement a workaround.
> >
> > AFAIU it's impossible to cut a branch for our projects and release a rc1
> > because of the release model we use. The release team does not allow us
> > to do that. We need to release directly a stable version and cut a
> > branch.
> >
> > I guess we'll do that in a couple of week, at release time.
> 
> That doesn't fit my understanding of cycle-with-intermediary, which is the
> the ceilometer release model per [0]. As I read the release model
> definitions [1], cycle-with-intermediary means that you can have
> intermediate releases *as well*, but you still have to have a cycle-ending
> release in line with the projects using the cycle-with-milestones model.
> 
> Can someone on the release team clarify this for us?

That's correct the bit you're missing is cycle-with-intermediary doesn't
have pre-releases (b{1,2,3},rc{1,2}) so when the ceilometer team feels
they have the code in shape for a release they'll tag that release and
cut a stable/pike branch at the tag point.

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[William M Edmonds]

Julien Danjou <jul...@danjou.info> wrote on 08/16/2017 02:13:10 PM:
> From: Julien Danjou <jul...@danjou.info>
> To: "Eric S Berglund" <esber...@us.ibm.com>
> Cc: openstack-dev@lists.openstack.org
> Date: 08/16/2017 02:14 PM
> Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer
> stable/pike branch outlook
>
> On Wed, Aug 16 2017, Eric S Berglund wrote:
>
> Hi Eric,
>
> > Is there an outlook for cutting a pike branch for ceilometer?
> > We currently can't run our 3rd party CI against pike without a pike
> > release branch and are deciding whether it's worth the time to
> > implement a workaround.
>
> AFAIU it's impossible to cut a branch for our projects and release a rc1
> because of the release model we use. The release team does not allow us
> to do that. We need to release directly a stable version and cut a
> branch.
>
> I guess we'll do that in a couple of week, at release time.

That doesn't fit my understanding of cycle-with-intermediary, which is the
the ceilometer release model per [0]. As I read the release model
definitions [1], cycle-with-intermediary means that you can have
intermediate releases *as well*, but you still have to have a cycle-ending
release in line with the projects using the cycle-with-milestones model.

Can someone on the release team clarify this for us?

[0]
https://github.com/openstack/releases/blob/bf890914c1ec5bcd41d70140e80ef8d39df64c86/deliverables/pike/ceilometer.yaml#L3
[1] https://releases.openstack.org/reference/release_models.html
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[Julien Danjou]

On Wed, Aug 16 2017, Eric S Berglund wrote:

Hi Eric,

> Is there an outlook for cutting a pike branch for ceilometer?
> We currently can't run our 3rd party CI against pike without a pike
> release branch and are deciding whether it's worth the time to
> implement a workaround.

AFAIU it's impossible to cut a branch for our projects and release a rc1
because of the release model we use. The release team does not allow us
to do that. We need to release directly a stable version and cut a
branch.

I guess we'll do that in a couple of week, at release time.

-- 
Julien Danjou
// Free Software hacker
// https://julien.danjou.info


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

[Eric S Berglund]

 
Hi all,
 
Is there an outlook for cutting a pike branch for ceilometer?
We currently can't run our 3rd party CI against pike without a pike
release branch and are deciding whether it's worth the time to
implement a workaround.
 
Regards,
Eric Berglund
-
E-mail: esber...@us.ibm.com


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev