Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Doug Hellmann]

Excerpts from Steven Dake (stdake)'s message of 2016-10-19 02:32:21 +:
> Doug,
> 
> Kolla rc3 is available in the queue by the hard deadline (more or less).  I 
> have a quick Q - would I need to submit another 3.0.0 patch with the same git 
> commit id, or does the release team do that automatically?

I will take care of the final patch. I'll prepare it later today and
then we will approve it tomorrow.

Doug

> 
> Regards
> -steve
> 
> On 10/7/16, 12:16 PM, "Doug Hellmann"  wrote:
> 
> >This week we tagged the final releases for projects using the
> >cycle-with-milestones release model. Projects using the cycle-trailing
> >model have two more weeks before their final release tags are due. In
> >the time between now and then, we expect those projects to be preparing
> >and tagging release candidates.
> >
> >Just as with the milestone-based projects, we want to manage the number,
> >frequency, and timing of release candidates for cycle-trailing projects.
> >With that in mind, I would like to propose the following rough timeline
> >(my apologies for not preparing this sooner):
> >
> >10 Oct -- All cycle-trailing projects tag at least their first RC.
> >13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
> >18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
> >20 Oct -- Re-tag the final RCs as a final release.
> >
> >Between the first and later release candidates, any translations and
> >bug fixes should be merged.
> >
> >We want to leave a few days between the last release candidate and
> >the final release so that downstream consumers of the projects can
> >report issues against stable artifacts. Given the nature of most
> >of our trailing projects, and the lateness of starting to discuss
> >these deadlines, I don't think we need the same amount of time as
> >we usually set aside for the milestone-based projects. Based on
> >that assumption, I've proposed a 1 week soft goal and a 2 day hard
> >deadline.
> >
> >Let me know what you think,
> >Doug
> >
> >Newton schedule: https://releases.openstack.org/newton/schedule.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

__
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][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Steven Dake (stdake)]

Doug,

Kolla rc3 is available in the queue by the hard deadline (more or less).  I 
have a quick Q - would I need to submit another 3.0.0 patch with the same git 
commit id, or does the release team do that automatically?

Regards
-steve





On 10/7/16, 12:16 PM, "Doug Hellmann"  wrote:

>This week we tagged the final releases for projects using the
>cycle-with-milestones release model. Projects using the cycle-trailing
>model have two more weeks before their final release tags are due. In
>the time between now and then, we expect those projects to be preparing
>and tagging release candidates.
>
>Just as with the milestone-based projects, we want to manage the number,
>frequency, and timing of release candidates for cycle-trailing projects.
>With that in mind, I would like to propose the following rough timeline
>(my apologies for not preparing this sooner):
>
>10 Oct -- All cycle-trailing projects tag at least their first RC.
>13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
>18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
>20 Oct -- Re-tag the final RCs as a final release.
>
>Between the first and later release candidates, any translations and
>bug fixes should be merged.
>
>We want to leave a few days between the last release candidate and
>the final release so that downstream consumers of the projects can
>report issues against stable artifacts. Given the nature of most
>of our trailing projects, and the lateness of starting to discuss
>these deadlines, I don't think we need the same amount of time as
>we usually set aside for the milestone-based projects. Based on
>that assumption, I've proposed a 1 week soft goal and a 2 day hard
>deadline.
>
>Let me know what you think,
>Doug
>
>Newton schedule: https://releases.openstack.org/newton/schedule.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
__
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][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Doug Hellmann]

Excerpts from Alexey Shtokolov's message of 2016-10-11 00:18:24 +0300:
> Doug,
> 
> We've finally fixed the blockers and tagged RC1 for all our repos.
> We're going to have final RC this Friday (Oct14).
> 
> Could I ask you to create stable/newton branches for repos:
> - openstack/fuel-agent
> - openstack/fuel-astute
> - openstack/fuel-library
> - openstack/fuel-main
> - openstack/fuel-menu
> - openstack/fuel-nailgun-agent
> - openstack/fuel-ostf
> - openstack/fuel-qa
> - openstack/fuel-ui
> - openstack/fuel-virtualbox
> - openstack/fuel-web
> based on the tag 10.0.0rc1
> 
> Or should I do it myself?

The release team will create the branches for you. The scripts we have
to do that will submit some additional patches to update the .gitreview
file, any constraints URLs in tox.ini, and reno (where that applies).

Please just include the request to have the branches created in the
commit message with the RC tag request. If you have some repositories
you want branched and others you do not, please separate those into two
patches to openstack/releases (the tool for creating the branches looks
at all of the deliverable files modified in a patch).

Doug

> 
> Best regards,
> Alexey Shtokolov
> 
> On Fri, Oct 7, 2016 at 10:16 PM, Doug Hellmann 
> wrote:
> 
> > This week we tagged the final releases for projects using the
> > cycle-with-milestones release model. Projects using the cycle-trailing
> > model have two more weeks before their final release tags are due. In
> > the time between now and then, we expect those projects to be preparing
> > and tagging release candidates.
> >
> > Just as with the milestone-based projects, we want to manage the number,
> > frequency, and timing of release candidates for cycle-trailing projects.
> > With that in mind, I would like to propose the following rough timeline
> > (my apologies for not preparing this sooner):
> >
> > 10 Oct -- All cycle-trailing projects tag at least their first RC.
> > 13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
> > 18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
> > 20 Oct -- Re-tag the final RCs as a final release.
> >
> > Between the first and later release candidates, any translations and
> > bug fixes should be merged.
> >
> > We want to leave a few days between the last release candidate and
> > the final release so that downstream consumers of the projects can
> > report issues against stable artifacts. Given the nature of most
> > of our trailing projects, and the lateness of starting to discuss
> > these deadlines, I don't think we need the same amount of time as
> > we usually set aside for the milestone-based projects. Based on
> > that assumption, I've proposed a 1 week soft goal and a 2 day hard
> > deadline.
> >
> > Let me know what you think,
> > Doug
> >
> > Newton schedule: https://releases.openstack.org/newton/schedule.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
> >

__
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][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Doug Hellmann]

Excerpts from Steven Dake (stdake)'s message of 2016-10-07 20:39:04 +:
> Doug,
> 
> We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at 
> present) and ack on 20th for retag of  final rc.  We expect our rc2 to be 
> final.

Right, I should have phrased that as a deadline for anyone who hadn't
already tagged RC1.

> If there are critical bugs that make the release doa in some way (such as 
> upgrades, reconfigure etc), we will obviously have to tag an rc3 to then 
> retag that as final.  I don’t expect that to happen but it is a possibility.

That's consistent with what we do for the milestone-based projects.

Doug

> 
> Regards
> -steve
> 
> 
> From: Doug Hellmann 
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Date: Friday, October 7, 2016 at 12:16 PM
> To: openstack-dev 
> Subject: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] 
> proposed deadlines for cycle-trailing projects
> 
> This week we tagged the final releases for projects using the
> cycle-with-milestones release model. Projects using the cycle-trailing
> model have two more weeks before their final release tags are due. In
> the time between now and then, we expect those projects to be preparing
> and tagging release candidates.
> 
> Just as with the milestone-based projects, we want to manage the number,
> frequency, and timing of release candidates for cycle-trailing projects.
> With that in mind, I would like to propose the following rough timeline
> (my apologies for not preparing this sooner):
> 
> 10 Oct -- All cycle-trailing projects tag at least their first RC.
> 13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
> 18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
> 20 Oct -- Re-tag the final RCs as a final release.
> 
> Between the first and later release candidates, any translations and
> bug fixes should be merged.
> 
> We want to leave a few days between the last release candidate and
> the final release so that downstream consumers of the projects can
> report issues against stable artifacts. Given the nature of most
> of our trailing projects, and the lateness of starting to discuss
> these deadlines, I don't think we need the same amount of time as
> we usually set aside for the milestone-based projects. Based on
> that assumption, I've proposed a 1 week soft goal and a 2 day hard
> deadline.
> 
> Let me know what you think,
> Doug
> 
> Newton schedule: https://releases.openstack.org/newton/schedule.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][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Alexey Shtokolov]

Doug,

We've finally fixed the blockers and tagged RC1 for all our repos.
We're going to have final RC this Friday (Oct14).

Could I ask you to create stable/newton branches for repos:
- openstack/fuel-agent
- openstack/fuel-astute
- openstack/fuel-library
- openstack/fuel-main
- openstack/fuel-menu
- openstack/fuel-nailgun-agent
- openstack/fuel-ostf
- openstack/fuel-qa
- openstack/fuel-ui
- openstack/fuel-virtualbox
- openstack/fuel-web
based on the tag 10.0.0rc1

Or should I do it myself?

Best regards,
Alexey Shtokolov

On Fri, Oct 7, 2016 at 10:16 PM, Doug Hellmann 
wrote:

> This week we tagged the final releases for projects using the
> cycle-with-milestones release model. Projects using the cycle-trailing
> model have two more weeks before their final release tags are due. In
> the time between now and then, we expect those projects to be preparing
> and tagging release candidates.
>
> Just as with the milestone-based projects, we want to manage the number,
> frequency, and timing of release candidates for cycle-trailing projects.
> With that in mind, I would like to propose the following rough timeline
> (my apologies for not preparing this sooner):
>
> 10 Oct -- All cycle-trailing projects tag at least their first RC.
> 13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
> 18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
> 20 Oct -- Re-tag the final RCs as a final release.
>
> Between the first and later release candidates, any translations and
> bug fixes should be merged.
>
> We want to leave a few days between the last release candidate and
> the final release so that downstream consumers of the projects can
> report issues against stable artifacts. Given the nature of most
> of our trailing projects, and the lateness of starting to discuss
> these deadlines, I don't think we need the same amount of time as
> we usually set aside for the milestone-based projects. Based on
> that assumption, I've proposed a 1 week soft goal and a 2 day hard
> deadline.
>
> Let me know what you think,
> Doug
>
> Newton schedule: https://releases.openstack.org/newton/schedule.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
>
__
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][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Steven Dake (stdake)]

Doug,

Just a follow-up, we will definitely have to tag a Kolla rc3 because on the 
following issue:
https://review.openstack.org/#/c/382470/1

Global requirements pushed a change into our repo and the core reviewer team 
acked it.  Unfortunately, we had no Newton branch (which is good – we have over 
80 bug fixes already in progress or merged in rc2).  I think there is a hole in 
the process here somewhere with release-trailing projects.  The problem is we 
can’t push this revert of our requirements update because we are not on the 
Newton branch (but on master instead).  Its not a super big deal, we are just 
going to revert it in the newton branch after creation which will ensure we 
have the correct Newton requirements used across OpenStack in Kolla.

I suspect the release team will want to fine-tune (or is already managing this 
situation) as to how the scheduling works with release-trailing projects and 
the mechanics of the branching.  If you need any help or advice or there is a 
summit session on the topic, let me know – happy to attend.  I am not sure what 
is optimal – I can shoot down ideas that wouldn’t work for this release 
classification tag pretty easily; have harder time coming up with optimal 
solutions because I lack the context the release team has.

Regards
-steve


From: "Steven Dake (stdake)" <std...@cisco.com>
Date: Friday, October 7, 2016 at 1:39 PM
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] 
proposed deadlines for cycle-trailing projects

Doug,

We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at 
present) and ack on 20th for retag of  final rc.  We expect our rc2 to be final.

If there are critical bugs that make the release doa in some way (such as 
upgrades, reconfigure etc), we will obviously have to tag an rc3 to then retag 
that as final.  I don’t expect that to happen but it is a possibility.

Regards
-steve


From: Doug Hellmann <d...@doughellmann.com>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org>
Date: Friday, October 7, 2016 at 12:16 PM
To: openstack-dev <openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] 
proposed deadlines for cycle-trailing projects

This week we tagged the final releases for projects using the
cycle-with-milestones release model. Projects using the cycle-trailing
model have two more weeks before their final release tags are due. In
the time between now and then, we expect those projects to be preparing
and tagging release candidates.

Just as with the milestone-based projects, we want to manage the number,
frequency, and timing of release candidates for cycle-trailing projects.
With that in mind, I would like to propose the following rough timeline
(my apologies for not preparing this sooner):

10 Oct -- All cycle-trailing projects tag at least their first RC.
13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
20 Oct -- Re-tag the final RCs as a final release.

Between the first and later release candidates, any translations and
bug fixes should be merged.

We want to leave a few days between the last release candidate and
the final release so that downstream consumers of the projects can
report issues against stable artifacts. Given the nature of most
of our trailing projects, and the lateness of starting to discuss
these deadlines, I don't think we need the same amount of time as
we usually set aside for the milestone-based projects. Based on
that assumption, I've proposed a 1 week soft goal and a 2 day hard
deadline.

Let me know what you think,
Doug

Newton schedule: https://releases.openstack.org/newton/schedule.html

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org<mailto: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][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Steven Dake (stdake)]

Doug,

We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at 
present) and ack on 20th for retag of  final rc.  We expect our rc2 to be final.

If there are critical bugs that make the release doa in some way (such as 
upgrades, reconfigure etc), we will obviously have to tag an rc3 to then retag 
that as final.  I don’t expect that to happen but it is a possibility.

Regards
-steve


From: Doug Hellmann 
Reply-To: "OpenStack Development Mailing List (not for usage questions)" 

Date: Friday, October 7, 2016 at 12:16 PM
To: openstack-dev 
Subject: [openstack-dev] [release][ansible][fuel][kolla][puppet][tripleo] 
proposed deadlines for cycle-trailing projects

This week we tagged the final releases for projects using the
cycle-with-milestones release model. Projects using the cycle-trailing
model have two more weeks before their final release tags are due. In
the time between now and then, we expect those projects to be preparing
and tagging release candidates.

Just as with the milestone-based projects, we want to manage the number,
frequency, and timing of release candidates for cycle-trailing projects.
With that in mind, I would like to propose the following rough timeline
(my apologies for not preparing this sooner):

10 Oct -- All cycle-trailing projects tag at least their first RC.
13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
20 Oct -- Re-tag the final RCs as a final release.

Between the first and later release candidates, any translations and
bug fixes should be merged.

We want to leave a few days between the last release candidate and
the final release so that downstream consumers of the projects can
report issues against stable artifacts. Given the nature of most
of our trailing projects, and the lateness of starting to discuss
these deadlines, I don't think we need the same amount of time as
we usually set aside for the milestone-based projects. Based on
that assumption, I've proposed a 1 week soft goal and a 2 day hard
deadline.

Let me know what you think,
Doug

Newton schedule: https://releases.openstack.org/newton/schedule.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

__
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][ansible][fuel][kolla][puppet][tripleo] proposed deadlines for cycle-trailing projects

[Emilien Macchi]

On Fri, Oct 7, 2016 at 3:16 PM, Doug Hellmann  wrote:
> This week we tagged the final releases for projects using the
> cycle-with-milestones release model. Projects using the cycle-trailing
> model have two more weeks before their final release tags are due. In
> the time between now and then, we expect those projects to be preparing
> and tagging release candidates.
>
> Just as with the milestone-based projects, we want to manage the number,
> frequency, and timing of release candidates for cycle-trailing projects.
> With that in mind, I would like to propose the following rough timeline
> (my apologies for not preparing this sooner):
>
> 10 Oct -- All cycle-trailing projects tag at least their first RC.
> 13 Oct -- Soft deadline for cycle-trailing projects to tag a final RC.
> 18 Oct -- Hard deadline for cycle-trailing projects to tag a final RC.
> 20 Oct -- Re-tag the final RCs as a final release.

I'm ok with this schedule. We're having some blockers in TripleO,
mostly under control but still not merged in our source code.
I thought we could release RC3 today but it's pointless given the fact
we still have critical bugs open.

This proposal would help us to reduce the list of bugs and make a
better release.

> Between the first and later release candidates, any translations and
> bug fixes should be merged.
>
> We want to leave a few days between the last release candidate and
> the final release so that downstream consumers of the projects can
> report issues against stable artifacts. Given the nature of most
> of our trailing projects, and the lateness of starting to discuss
> these deadlines, I don't think we need the same amount of time as
> we usually set aside for the milestone-based projects. Based on
> that assumption, I've proposed a 1 week soft goal and a 2 day hard
> deadline.
>
> Let me know what you think,
> Doug
>
> Newton schedule: https://releases.openstack.org/newton/schedule.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



-- 
Emilien Macchi

__
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