The following is adapted from a room ping in the Ubuntu Flavors channel. If you aren’t a member already, feel free to join!
We are now one week away from Plucky’s Feature Freeze:
- The week following that will be an Ubuntu Testing Week, with Beta planned for March 27th, a little more than a month away. Should your flavor start working on documentation or announcement text to supplement that?
- Debian Trixie is starting to stabilize as well. Please keep this in mind when planning transitions and major changes, both for Ubuntu and Debian. This means that Debian Import Freeze will be stopped for the cycle approximately 3 weeks before Debian Trixie’s Transition and Toolchain Freeze, so I suspect we’re going to be seeing a few last-minute transitions in Debian. This also means we need to be careful about syncs in that three weeks afterwards, so we don’t run into accidentally-started transitions. Does your flavor need to start any remaining transitions this cycle?
- I’m working on finishing up a few transitions now, from what I know there’s at least Ocaml, Qt, GNOME, KDE Plasma, KDE PIM, libgit2, and a few misc like openssl are on my list. I want to assert this now, a week ahead of time: historically, the rule has been, anything that hits proposed up to the exact time/date of Feature Freeze is fair game. Meaning, you don’t have to stress about everything migrating before Feature Freeze, as long as it’s in -proposed. (Please, don’t take this as a free pass to disregard normal standards.) Has your flavor been able to properly strike a balance between uploading a lot of new software and not enough?
- If you follow plucky-changes, you’ll know that we’ve been having a merge party. Has your flavor evaluated the outstanding merges for your packages, and do any items need a merge pre-FF?
- Only 12 bugs are targeted for the Feature Freeze milestone at this point; I’d suggest that everyone occasionally takes a peek at that to catch any surprises. I have a few. And please, feel free to target bugs to that milestone if it must be fixed before Feature Freeze. Does your flavor have any bugs that need to be fixed before Feature Freeze?
- Your daily images don’t need to be perfect yet, especially in the context of the LTS point release and the temporary reallocation of testing resources, but it’s a good idea to at least do a smoke test. Has anyone provided feedback on your daily ISO lately, generally speaking?
The bottom line is, we’re starting to enter the stabilization period for Plucky. It’s worth deeply thinking about in the context of your flavor.
Thank you for everything you do! Let’s successfully release Plucky!