Complete rewrite of the openQA guide section on handling the
mass branching process. This splits it into sections to avoid it
being a long shaggy hard-to-read blob, and tries to make things
much more concrete and step-by-step based on experience from the
last two cycles.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Fix a bunch of errors and warnings:
Fixed two errors:
ERROR (asciidoctor): target of xref not found: epel:epel-policy.adoc#policy_for_end_of_life_releases
ERROR (asciidoctor): target of xref not found: fedora-docs::contributing-docs/asciidoc-markup.adoc
By linking to the URL directly, e.g. https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/asciidoc-markup/
this is how it is done in many other locations in this document, so just
following that precedent.
fixed this warning:
WARN (asciidoctor): skipping reference to missing attribute: stable
there was no "stable" attribute, there was "current" so changed that to
that
Fixed 6 of the following warnings like:
WARN (asciidoctor): list item index: expected 1, got 2
Signed-off-by: Ryan Lerch <rlerch@redhat.com>
See infra/ansible#3119 -
there's really no need for FedoraBranchedBodhi to have as many
states as it does. This corrects the state we set it to at Beta
freeze / u-t activation and drops the setting of it to 'current'
at release time to match the simplification in that PR.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
* Split into two sections so we can run prepare-bodhi-repos.yml playbook
before bodhi-backend.yml, otherwise it breaks new-updates-sync
* Set released-on field of new release
* Set version field of new release
* Add step to edit branch field of the previous release
* Add steps redeploy bodhi pods and restart services
Most of the previous text in this section isn't needed, as it refers to
things that are covered by variable changes now. Move it to the
preparatory section and rewrite it to cover the changes that are needed.
* Move pre-announcement to a week before
* Add reference to previous announcement
* Add step to announce start of branching
* Add step to announce end of branching
This adds info about needing to resign eln with the new rawhide key
fixes places that refered to a bad/old path for scripts
removes adding a container release in bodhi which we don't use anymore.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I've tried to adjust any places in our docs where we were pointing to a
specific ticket to the new forge link. Also, any places that mentioned
where tickets are located.
The tickets sop needs a ton of work, I will do that in another PR.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
I am not sure why this was in here. There shouldn't be any need to edit
the index files when you revoke a cert, so just drop this.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Refer to rhel10 instead of 6 or 7.
Explain that passwords are in ansible-private now.
Add info about where kickstarts are in ansible and how
they are named.
Fixes infra/docs#74
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Use correct url
Use correct matrix room
No longer using vm's, but depoloyed in openshift
Note the groups you need to be in to edit releases.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This hasn't happened in... many many years.
If it does, the weekly check will catch it and we can look at it from
there.
Fixes infra/docs#67
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
