Missed one place where the stein release date was referring to Thursday
and not Wednesday, and incorrectly set cycle-trailing to be two months
instead of three.
Change-Id: I8f4e40cece4aca8f5b49237a0276e35400c4aa94
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This sets the end date for the Rocky key, adds the Stein key
starting today and links to a minimal export of the corresponding
public key and its details on the keyserver network. The key
material change (Depends-On below) merged and went into effect
2018-09-05.
Change-Id: Ia345d6264528e069a1b3e61b88f616f9e9389438
Depends-On: https://review.openstack.org/599092
Update process document to reflect changes in the cycle-trailing
deadline.
Change-Id: I428991368f02f2aeaa5dfb8303bbe4b040ba97b7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Community goals acknowledgement was missing the release name resulting
in a cut off sentence in the Stein schedule descriptions. Adds the
missing name.
Change-Id: Ie75b36d9350adaf8bb6d95ae89c454e7b7721bc8
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This adds some deadline information to the Stein schedule so teams can
plan when they need to gather these in time for inclusion.
Change-Id: I9e1a4ab132e973e97415a35b102114071ea403a8
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Massage some wording in the Stein schedule so we have something to
update and force republishing to the site.
Change-Id: Ibabacffa93a9b2089f03e3fd12e4d60ed501954d
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
The OpenStack Summit Berlin will be held on November 13-15, 2018.
It will be in R-21, not in R-22.
Change-Id: Iddcf65c2bfe0656f79abbff16f2bc5d9d0a20800
Sometimes creating the branches immediately for projects can comes as a
surprise and cause a little extra work with backports when they have
critical fixes to include with a requirements FFE. To avoid some of
this, change the branch creation policy to allow it at freeze time but
do not enforce it as a requirement. Then create the branches for any
missed deliverables closer to the end of the cycle.
Change-Id: Ib6f4037c450a00080a5e9a2a7665c6ea4d112ba5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Include stein in the index page list. This also adds support for
a "future" status since validation was add/changed since the
start of the last cycle.
Change-Id: Ie1fc997c1f5f0f3c6af1d048fcc4b25a4608e70f
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Move our process document into the reference guide published on the
website so it is easier to provide folks with links to explain the
various stages of the cycle.
Adding the new page also requires fixing up some RST warnings so
Sphinx would run properly, and fixing some markup so the rendered page
looked OK.
Change-Id: If6280b60b8802d3908c233a30547ec442cb2804e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Per [1], Oslo observes feature freeze earlier than most projects in
order to give consuming projects a chance to implement any new
features in Oslo before their feature freeze. This should be
reflected in the release schedule.
Change-Id: Ib822c34c1ade20dcdaa5c9667f91e0639e0f56df
1: http://specs.openstack.org/openstack/oslo-specs/specs/policy/feature-freeze.html
Adds bolded headers for the Reviewer Guide
that matches what headers reviewers should
be looking for when reviewing. Also adds
minor edits for grammar and clarity.
Change-Id: I098a8d8a04576023d7f13d84a86e8e33ac0d2ca8
There were a few typos and other small changes mentioned in the review
of https://review.openstack.org/#/c/579019. This patch fixes those.
Change-Id: I928e8f0930c4fb405d6947d82883fa48a5185dfc
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Reference documentation was alpha-ordered. Reorder it so
that user documentation is first and reviewer documentation
last. If people only read one thing, it should be how to
use that repository.
Change-Id: Idc82d6542b11cf229493e18e0af3f1a582cc3b9d
Move the existing content for contributors wanting to propose releases
out of the readme file and into the reference guide that we publish.
Change-Id: Ie90e09a5dd3eeac8c66511aa4b9567402cfa8282
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Remove the old content from the readme and add a new reviewer guide
section to the reference content that is published via sphinx.
Story: #2001838
Task: #12602
Change-Id: Ied7655d893f0eeb90ed2bdfbc249ea6df4991e96
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a proposed schedule for the Stein release extending
the cycle to 32 weeks to align with a combined Summit/PTG
event in March 2019.
Change-Id: Ic84a3a87d8ef53ae839a2c65cb553cf926f7663f
As we discussed today in our meeting, this patch tries to write down
the new policy we agreed to so we can remember what it is.
Change-Id: I4d460c226a20f4c8d657c8c88ab0b1ebfb233ee5
Story: #2001847
Task: #12615
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add an API to Deliverable to let the sphinxext inject the series status
information, since the build conditions and working directory are
different under sphinx.
Change-Id: Id2bbdc4815564d28a5f4989bf7c74aed93e8c129
Story: #2001852
Task: #12620
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Move the information about the series status into a data file and use
that to generate the table on the main page. This is the first step
toward adding deliverable-specific series status information to the
output, since we need a place to put the default values.
Because we're adding a yaml file under the deliverables directory that
is not actually a deliverable file, we have to update the validation
tool to ignore it.
Story: #2001852
Task: #14347
Change-Id: I99bd94a323b53c0dfc2cb648268e51a30321cd46
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Due to new Stable policy [1] the release table needs to be updated.
[1] https://review.openstack.org/#/c/552733/
Change-Id: I0be6cf2e5658277e3f41bf0549198c69c9925a9a
This patch adds the dates to the Rocky release
calendar that were decided upon here [1].
[1]https://review.openstack.org/#/c/551404/
Story: 2001611
Task: 12049
Change-Id: Iaafe2e4e52b83c5f01a87a60cbcde0fc1c138875
There is no reason to impose a short deadline for packaging
or lifecycle management projects that want to trail the
release. Let's relax the constraints and accept that
cycle-trailing releases can happen up to 3 months after the
main components synchronized release.
Additionally, the idea behind the membership check at
milestone-2 is to protect packagers against late additions,
not to prevent late-added packaging systems from doing a
release. The new rules should also apply to Queens, so that
OpenStack-Helm and LOCI can actually do a Queens packaging
release, despite having been added post milestone-2.
Change-Id: If997e6053af6e74bf6ce8755313346effca6b4e5
The artifact signing key for the Rocky development cycle has been
generated and is ready to rotate into production as soon as
cycle-trailing releases for Queens have concluded.
Change-Id: I40a609d411b73f685c062577a7baf5dd2212ff5c
Depends-On: https://review.openstack.org/551406
In the release-cycles/Support length discussion at the PTG we (mostly)
all agreeed to keep Ocata around for another 6 months so remove the EOL
tag and set the clock ticking.
It looks strange that we only extended Ocata but it's the first step in
a longer process that will probably still be on-going at the Berlin
summit
Change-Id: Ib09b27eff0e6ef94ddf4a1f6291b16b4a1b40c8c
