Re: [openstack-dev] [release] Release countdown for week R-5, Jan 16-20

2017-01-13 Thread joehuang
Great, got it, thanks a lot

Best Regards
Chaoyi Huang (joehuang)


From: Doug Hellmann [d...@doughellmann.com]
Sent: 13 January 2017 22:55
To: openstack-dev
Subject: Re: [openstack-dev] [release] Release countdown for week R-5,  Jan 
16-20

Excerpts from joehuang's message of 2017-01-13 01:23:08 +:
> Hello, Doug,
>
> One question, according to the guide for self-branch[1], the Ocata stable 
> branch should be created for RC1 tag for projects using the 
> cycle-with-milestone release model. The date for RC1 one is Jan 30 - Feb 03 
> according to the schedule [2]. Tricircle is one big-tent project with  
> cycle-with-intermediary mode, and has dependency on stable Neutron, should 
> Tricircle Ocata stable branch be created during  Jan 30 - Feb 03 or later 
> than Feb 03? I think Neutron Ocata stable branch will be created during Jan 
> 30 - Feb 03.

You'll probably want to wait until after the Neutron stable branch has
been created. You can submit the branch request and either mark it WIP
or add a Depends-On to prevent it from merging before the neutron
request.

Doug

>
> [1]http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n66
> [2] https://releases.openstack.org/ocata/schedule.html
>
> Best Regards
> Chaoyi Huang (joehuang)
>
> 
> From: Doug Hellmann [d...@doughellmann.com]
> Sent: 13 January 2017 2:34
> To: openstack-dev
> Subject: [openstack-dev] [release] Release countdown for week R-5, Jan 16-20
>
> Focus
> -
>
> Feature work and major refactoring should be starting to wrap up
> as we approach the third milestone and various feature and release
> freeze dates.
>
> The deadline for non-client library releases is Thursday 19 Jan.
> We do not grant Feature Freeze Extensions for any libraries, so
> that is a hard freeze date. Any feature work that requires updates
> to non-client libraries should be prioritized so it can be completed
> by that time.
>
> Release Tasks
> -
>
> As we did at the end of Newton, when the time comes to create
> stable/ocata branches they will be configured so that members of
> the $project-release group in gerrit have permission to approve
> patches.  This group should be a small subset of the core review
> team, aware of the priorities and criteria for patches to be approved
> as we work toward release candidates. Release liaisons should ensure
> that these groups exist in gerrit and that their membership is
> correct for this cycle.  Please coordinate with the release management
> team if you have any questions.
>
> General Notes
> -
>
> We will start the soft string freeze during R-4 (23-27 Jan). See
> https://releases.openstack.org/ocata/schedule.html#o-soft-sf for
> details
>
> The release team is now publishing the release calendar using ICS.
> Subscribe your favorite calendaring software to
> https://releases.openstack.org/schedule.ics for automatic updates.
>
> Important Dates
> ---
>
> Final release of non-client libraries: 19 Jan
>
> Ocata 3 Milestone, with Feature and Requirements Freezes: 26 Jan
>
> Ocata release schedule: http://releases.openstack.org/ocata/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] Release countdown for week R-5, Jan 16-20

2017-01-13 Thread Doug Hellmann
Excerpts from joehuang's message of 2017-01-13 01:23:08 +:
> Hello, Doug,
> 
> One question, according to the guide for self-branch[1], the Ocata stable 
> branch should be created for RC1 tag for projects using the 
> cycle-with-milestone release model. The date for RC1 one is Jan 30 - Feb 03 
> according to the schedule [2]. Tricircle is one big-tent project with  
> cycle-with-intermediary mode, and has dependency on stable Neutron, should 
> Tricircle Ocata stable branch be created during  Jan 30 - Feb 03 or later 
> than Feb 03? I think Neutron Ocata stable branch will be created during Jan 
> 30 - Feb 03.

You'll probably want to wait until after the Neutron stable branch has
been created. You can submit the branch request and either mark it WIP
or add a Depends-On to prevent it from merging before the neutron
request.

Doug

> 
> [1]http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n66
> [2] https://releases.openstack.org/ocata/schedule.html
> 
> Best Regards
> Chaoyi Huang (joehuang)
> 
> 
> From: Doug Hellmann [d...@doughellmann.com]
> Sent: 13 January 2017 2:34
> To: openstack-dev
> Subject: [openstack-dev] [release] Release countdown for week R-5, Jan 16-20
> 
> Focus
> -
> 
> Feature work and major refactoring should be starting to wrap up
> as we approach the third milestone and various feature and release
> freeze dates.
> 
> The deadline for non-client library releases is Thursday 19 Jan.
> We do not grant Feature Freeze Extensions for any libraries, so
> that is a hard freeze date. Any feature work that requires updates
> to non-client libraries should be prioritized so it can be completed
> by that time.
> 
> Release Tasks
> -
> 
> As we did at the end of Newton, when the time comes to create
> stable/ocata branches they will be configured so that members of
> the $project-release group in gerrit have permission to approve
> patches.  This group should be a small subset of the core review
> team, aware of the priorities and criteria for patches to be approved
> as we work toward release candidates. Release liaisons should ensure
> that these groups exist in gerrit and that their membership is
> correct for this cycle.  Please coordinate with the release management
> team if you have any questions.
> 
> General Notes
> -
> 
> We will start the soft string freeze during R-4 (23-27 Jan). See
> https://releases.openstack.org/ocata/schedule.html#o-soft-sf for
> details
> 
> The release team is now publishing the release calendar using ICS.
> Subscribe your favorite calendaring software to
> https://releases.openstack.org/schedule.ics for automatic updates.
> 
> Important Dates
> ---
> 
> Final release of non-client libraries: 19 Jan
> 
> Ocata 3 Milestone, with Feature and Requirements Freezes: 26 Jan
> 
> Ocata release schedule: http://releases.openstack.org/ocata/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] Release countdown for week R-5, Jan 16-20

2017-01-12 Thread joehuang
Hello, Doug,

One question, according to the guide for self-branch[1], the Ocata stable 
branch should be created for RC1 tag for projects using the 
cycle-with-milestone release model. The date for RC1 one is Jan 30 - Feb 03 
according to the schedule [2]. Tricircle is one big-tent project with  
cycle-with-intermediary mode, and has dependency on stable Neutron, should 
Tricircle Ocata stable branch be created during  Jan 30 - Feb 03 or later than 
Feb 03? I think Neutron Ocata stable branch will be created during Jan 30 - Feb 
03.

[1]http://git.openstack.org/cgit/openstack/releases/tree/README.rst#n66
[2] https://releases.openstack.org/ocata/schedule.html

Best Regards
Chaoyi Huang (joehuang)


From: Doug Hellmann [d...@doughellmann.com]
Sent: 13 January 2017 2:34
To: openstack-dev
Subject: [openstack-dev] [release] Release countdown for week R-5, Jan 16-20

Focus
-

Feature work and major refactoring should be starting to wrap up
as we approach the third milestone and various feature and release
freeze dates.

The deadline for non-client library releases is Thursday 19 Jan.
We do not grant Feature Freeze Extensions for any libraries, so
that is a hard freeze date. Any feature work that requires updates
to non-client libraries should be prioritized so it can be completed
by that time.

Release Tasks
-

As we did at the end of Newton, when the time comes to create
stable/ocata branches they will be configured so that members of
the $project-release group in gerrit have permission to approve
patches.  This group should be a small subset of the core review
team, aware of the priorities and criteria for patches to be approved
as we work toward release candidates. Release liaisons should ensure
that these groups exist in gerrit and that their membership is
correct for this cycle.  Please coordinate with the release management
team if you have any questions.

General Notes
-

We will start the soft string freeze during R-4 (23-27 Jan). See
https://releases.openstack.org/ocata/schedule.html#o-soft-sf for
details

The release team is now publishing the release calendar using ICS.
Subscribe your favorite calendaring software to
https://releases.openstack.org/schedule.ics for automatic updates.

Important Dates
---

Final release of non-client libraries: 19 Jan

Ocata 3 Milestone, with Feature and Requirements Freezes: 26 Jan

Ocata release schedule: http://releases.openstack.org/ocata/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