Add additional code and spec submission deadlines
that the manila project maintainers adhere to.
Change-Id: Ic004f20ece15be80f905d395def4d8d9962a91f5
Signed-off-by: Goutham Pacha Ravi <gouthampravi@gmail.com>
This adds the PTG to show up as a cross-project event.
Change-Id: I8a8551772a0f7074ca4ac1bc34449ddc03100940
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Devstack-gate has been restructured since we added references to patches
to show what needs to be done to prepare for new stable branches. This
is a trivial update to point to a more recent review that is a better
example of what needs to be done.
Change-Id: Iacffaf3dce12b3aaea113d057d497e19970d0fc2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This is a 26 week schedule for the Wallaby release. Planned release date
is April 14, 2021. We don't have a date set for a first half 2021 event,
but it is expected to be some time shortly after this date.
Change-Id: I6ba030f678879d32f99680c68dcd4bff9cc00032
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This does a new release with release-test to see if everything is
covered to allow branches to have a bugfix/* prefix.
Change-Id: I7869cf412524d7352249f02f7449b2fddf401d2c
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Information about adding a deliverable should live in the
general usage documentation, not the release models page.
Also stop advising projects to release independently if they
get added after the second milestone of a series, as it creates
issues down the road with inconsistent stale pages in the
'Independent' section.
Change-Id: I9319656b62b063d637737ad8667d3099f179fb58
Clarify language used in the page.
Only list teams with active deliverables (current or still
under maintenance) in the Teams section. This allows to stop
mentioning long-gone teams like Astara or Cue or Fuel.
Change-Id: Ic41020606febf69769825f904255c915784791a1
Now that releases are systematically proposed for deliverables with
changes at the end of a cycle, the cycle-automatic release model is
really better described with cycle-with-intermediary combined with
the 'stable-branch-type: none' option.
Change-Id: Ia9c5dadcaa89fbbdb7420a52cc3fed665e4ba513
Cycle-trailing deliverables are regular cycle-following deliverables,
using RCs or not not using RCs -- they just have a different deadline.
Rather than using a release model, those deadline variants are better
described using deliverable types, in much the same way 'library'
deliverables have a specific deadline too.
This simplifies the list of models significantly, and allows to have
proposer validation of trailing deliverables that use RCs or not use
RCs.
For compatibility in old branches, setting 'cycle-trailing' is still
supported, it will just overload the type to 'trailing' if specified.
Change-Id: Ifce88ef3e5dd406f45f25214699f16e736ad5377
Team pages on releases.o.o sort 'Independent' releases between
'Juno' and 'Icehouse', which is pretty confusing. List independent
releases last, if any.
Change-Id: If702f3b1d3fb4a2583172ce0946450b89a14d168
The highlights extension attempted to be helpful by pulling in team
details from governance into the generated highlights output. This did
not account for the possiblity that teams may actually leave official
OpenStack governance, and therefore may not have these details present
in the governance output.
This adds handling to fail gracefully in this scenario by just not
trying to include the information that is no longer there.
Change-Id: Iee97b9547a2044acd86864f788f7ba1294afbf0a
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Extended Maintenance does not mean by default that every project is
maintained. It could happen that a project is not actively maintained
or unmaintained or even it's team marked it as End of Life. This patch
adds a note to clarify that.
Also reformat a previous note.
Change-Id: Ib96cefe0645de1201fa06e9150a771d8ab94d2f9
This adds a new std-with-versions branch type. This is used to control
validation logic when branching to allow the Ironic team to create
intermediary stable branches based on major.minor version numbers in
addition to our normal expected stable/$series branches.
https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/new-release-model.html
Change-Id: Ic482c77a2c177162ffe37643a455ac1724a658b3
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This sets the end date for the Ussuri key, adds the Victoria key
starting today and links to a minimal export of the corresponding
public key and its details on the keyserver network. This can be
amended with a new patchset or a follow-up change to correct the
included dates after the key material change (Depends-On below)
merges and goes into effect.
Change-Id: Id58a72b73774aed79ebc429ad772634d0e779447
Depends-On: https://review.opendev.org/729804
This adds some steps to be done as we near the end of a development
cycle to make sure we are ready when stable branches are created.
Change-Id: I56ae71a6d9869ab138c256d9d3021dfd8fd1402e
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This adds a script that will go through all release reviews under a
given review topic, find the PTL and release liaisons for the owning
teams of those releases, and add them as reviewers to the patch.
Change-Id: I6294c1d9da7d6a977df6d8460aa085d2cc7e72a5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This makes sphinx-build use the number of cores available to make the
docs build parallel. On my 16 core system, this cut the time by ~50%. We
don't have as many cores available in the gate, but it should provide a
slight improvement in overall job time.
Change-Id: I7ad4d87a3dba10475a0fcf797a9aa2d4b1ad0eb5
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>