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
PTL nominations were listed the week of Queens-3, but they actually
do not start until the following week. A little late, but we should
change it to accurately reflect the right point on the schedule.
Change-Id: I60b27b76ca0d2022b1d09bfd3e801fe6de152436
Newton is EOL, but we have not updated the release table, so it still
shows up as active. This updates the release to show its final state.
Change-Id: Iceb608eb962d98d51ed11184f7450feb9101dc0f
We switched to a new logo some time ago, but since the releases
repo uses a customized doc theme it still had the old logo in
the generated HTML output.
This patch keeps the custom theme, but just switches out the old
logo for the new one.
Change-Id: I368ec2e31055d279b5701cfbbec8a78111e73cb2
Since the shade team is renamed, redirect the old team page location.
Change-Id: I7cc485365ef370ebc724c51557dd2c77b9e8c75e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This patch adds a new item to the schedule: email
deadline. It then adds that item, along with ptl nominatons
and ptl elections to the official schedule.
Change-Id: I433c4c51564ec0cd95302a1a14071c23a2bceba5
We had previously installed our docs dependencies as extras in
setup.cfg. Doc jobs are now changed to not install the project,
so these dependencies are no longer being installed.
With recent changes to the doc jobs, we need to specificy that python3
is used. Update the zuul config file for this.
Change-Id: Ie925efefb1126dbe7fa0a9f0f1727da01f48c512
Depends-on: Ib882a4d09898ff206b36ac8aef840bee0748368e
Assuming we will stay with a 6 month release cycle for Rocky,
this is a proposed schedule for the Rocky cycle.
One thing to note is the date for the S PTG has not been finalized
yet, so we may need or want to push out the window between one of
the milestones so there is not too long of a gap between Rocky
being released and the next PTG being held.
Change-Id: I0e26b443b7d4cf64f834b9726342cdfab54d36e7
This adds the ability to provide release highlights in the deliverable
yaml file. These highlights can then be extracted and displayed into
published documentation using a new 'cycle-highlights' directive.
Change-Id: I40791dad4b5a4d2c4089e5e43d52f00b52cc3217
Links were pointing under the tags information for a release model, should
be under the release_models governance info.
Change-Id: Ia7fc62cae517c3340a46deafe54e94746873314b
This patch adds the release milestones to the
schedule as agreed upon by the Cinder team at
the Queens PTG.
Change-Id: I7fe691b5642b897d2c0365e368e2909629580067
Since the Pike cycle releases are behind us, document that the
pending key for the Queens cycle is now in place as of 2017-09-15
and the Pike key is retired from use beyond that date.
Change-Id: I3c64ad3aaf10452ab6fb1b03014a5e2f571215d0
