We didn't actually want Train to go immediately into Extended
Maintenance. This fixes the transition date for Train to be 18 months
from its original release date.
Change-Id: I777a468c995c4f90852b9b14f6d188438357bc34
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
If we make Ussuri the future release, the htaccess will be generated
with redirections for it. When we decide that Train is maintained and
not developed, we should move Ussuri to development. And add 'Vancouver'
or something when we know the next series name to immediately generate
the new redirection.
Alternatively, we could change the code to generate the redirections
at all times. If the code is idempotent, we would never have an
issue of "forgotten" state of a series, and could bypass it.
Change-Id: I69008ebd330a90ae42166d55e5c06b694fc2d042
Recent merging of the liaison-loading code in list-changes makes
most list-changes job fail due to error in YAML loading code.
Beyond that YAML loading issue, the code assumes getting a dictionary
with team names as keys and an array of liaisons dictionary as values.
Fix the release_liaisons.yaml and schema to match.
Change-Id: I94fa41862d37aaf0535d64afd00b2bd55bb4649a
As it was discussed during Release Team meeting @ PTG the EM release
should happen somewhere around post release time.
Change-Id: Ibefd2b96cb3409267a8ed6b5e68b5b52255577b6
Adding liaisons to deliverables where there is a liasion listed here:
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Release_management
Also creates a data dir to put the non deliverable files that were in the
deliverables dir elsewhere and updates filepaths to reflect the change.
Story: 2005702
Task: 31024
Change-Id: Idc5f4b29dd375465b21d678fa8503cbd8d6d3eb6
