owner-sync-pkgdb needs some updating.
we need to update the hardcoded version numbers that maps to rawhide
we also need to update the cronjob to sync the new release

we need to send out some emails. we should send a reminder a week before, an email when we are starting and one when done. they should all go to devel-announce

pkgdb webui needs to be renabled to sync the acls and make the branches

We should start the koji tag creation process before we start pkgdb and allow it to run while we work on other steps

we need to make sure we branch comps

the new release targets fxx fxx-candidate and updated rawhide need to tag the resulting build into fxx-pending not fxx. we also need to document that we need to coordinate for auto signing

Although this is less important, I normally like to be around and help on the pkgdb side, but for this we should plan starting the mass-branching much earlier. IIRC it started around 10pm for me this time :(

there is missing steps in the sop for dealing with containers and making sure the base is setup correctly

pkgdb_sync_git_branches.py not changed on pkgs02.phx2.fp.org rather it is synced by running the ansible playbook.

updates-testing and updates empty repos not seeded

The nightly.sh pungi script in fedora-pungi didn't properly handle the case of the top dir being nonexistant. We should make sure it handles this so we don't get composes that finish and don't sync out.

We have no sop on how to branch the container world in osbs

This section of the mass branching points to an out of date procedure for Koji tasks. https://docs.pagure.org/releng/sop_mass_branching.html#koji

https://pagure.io/releng/blob/master/f/scripts/block_retired.py#_37 block_retired needs updated branch info

update the script that syncs updates and updates-testing repos to the master mirror

scripts/block_retired.py in the releng git repo needs updated to deal with new release mappings

-build tags need to be locked down with admin perms

tagging for meeting so that the issues can be discussed and work can be appropriately scoped

Discussed today in the Fedora Release Engineering meeting.

We no longer have packagedb; some contributors got together at DevConf to discuss and we are waiting to hear from them.

@kellin and @puiterwijk will make further contact in a few days if the discussion has not already started.

@mohanboddu will add this ticket to the Releng meeting on Thursday, May 10 to see if anything more is needed.

@mohanboddu asked me to mention here that I've temporarily added fedora-repos-rawhide-modular to the Server Edition definition in https://pagure.io/fedora-comps/pull-request/281 and we will need to revert this when we branch.

@mohanboddu will review this ticket and make sure all issues have been captured. Some issues we just need to remember to do them (add those to the SOP).

@mohanboddu still has followups to review and update docs.

@mohanboddu , which specific docs need review? Maybe could do together with @kellin . Add urls here.

@mohanboddu has to create the pull requests in a nicely documented way.

@mohanboddu reports that he is working on this this week.

@mohanboddu, what is the status of this work?

From our grooming discussion on #fedora-releng channel on Apr 12 2019

proposal: mboddu will try and get it done by end of next week and will be removing meeting tag

@mohanboddu and @humaton worked on this in August but need to update documentation due to recent changes.

I believe all changes are reflected in releng SOP closing.