whiteboard questions: * Does the RT need to track release tracking bugs or can this be left up to individual teams? - what happens if something fixed down in stack, critical. What happens in core. - extend use of rls-?-incoming, series targetted, rls-?-notfixing as an option? * Who liaises with flavours? - The release team in general. * Is someone in charge of the common section & coordination of the release notes? * Can freezes be done on an opt-in basis by flavors as desired? Planning: - PES Offspring Front End, kicking off CD builds by Flavor leads on demand, graduated authentication, backend commands. - Offspring is not used to drive cdimage backend today. Wanting to get Offspring on top of the current set of tools. What version of live-build? version per series. - Canonical cdimage folks still will retain shell access. - Raring wanting not to have to freeze for milestones or otherwise. Freezes useful for flavors: installability (possibly solved by daily quality push?), prevent people changing versions while releasing images. Also useful to change just a few things and know what's different between images when trying to get to a milestone. Software to tell only to freeze parts of the archive? Set of packages seeded in image possible freeze on just those packages. What about common set? Migration blacklist - Britney told to freeze things. Opt in? Chained dependencies to be Frozen as well. Uploads to -proposed, it's the freezing of the release pocket. (Migration Freeze). No coding, need to work on who can edit all the configuration. Won't hit release pockets. Milestones on day when testing resources available for flavor. Community testing and 2 week cadence. Kernel being frozen is concern - communication is going to be key here. All uploads go through -proposed now, see memo on ubuntu-devel-announce. Auto migrated to release pocket, once installable, no out of date binaries, and passes its autopkgtest suite (if it has one). (uses unstable -> testing software in debian) Release team is going to monitor closely for next month or so. No uninstallables in main Raring this morning but only working for 5 days. Release team manages conflicts between flavors. Flavors need to figure out what need to do, and come to release team to schedule. Extension to coordinate milestones on same cycle. Document release notes best practices - follow up online afterwards? Timing: infrastructure avaialbe this cycle. [ACTIONS] [laney] follow up on availability of source code for reports [all flavors] coordinate whether and when to do freezes so that any milestone freezes happen at the same time [persia] follow up on defining best practices for release notes collaboration