7098
Comment:
|
7098
|
Deletions are marked like this. | Additions are marked like this. |
Line 82: | Line 82: |
* [./] Prepare [[Teams/Publicity/Announcements|press release]] | * (./) Prepare [[Teams/Publicity/Announcements|press release]] |
This is a RM's TODO list for the Stretch release, which might not be authorative or complete.
The following things need to be done for the Stretch release:
Tagging RC Bugs
At some point, we will have to tag the remaining RC bugs to filter what should be removed/deferred/fixed. The usertagged bugs will be listed on:
Actions to do before the freeze
Decide on a code name for <codename>+2
Theme (artwork) design should be finalised and decided
Prepare the website changes
Ensure that the following pages exist on debian.org/releases/<RELEASENAME>
index
credits
errata
installmanual (requires installmanual is being built for RELEASE as well)
releasenotes (requires releasenotes is being built for RELEASE as well)
reportingbugs
There should also be a page for debian.org/releases/<RELEASENAME+1> as there are some links to it.
The pages should say they are beta versions/not released etc. at this point
Assert the architecture list is up to date (release.data), new ports should be available on https://debian.org/ports (ports/index.wml)
Decide on Release Architectures
Have FTP masters create security + backports archive for upcoming release
Have DSA upgrade a non-critical machine
Suggestions include: lindsay.debian.org (the host doing the lintian archive-wide run)
Have DSA upgrade a buildd for each architecture
- kvm/virtual (upgrade or create new vm)
all
amd64/i386
arm64 (some of them, they could probably also build armhf)
ppc64el
- bare metal
arm64 (some of them are bare metal)
armel/armhf
mips
mipsel/mips64el
s390x (not virtual from the DSA point of view)
- kvm/virtual (upgrade or create new vm)
Before the Release
binNMU everything that has a Built-Using header and is using old versions to remove old source packages from the release.
- pochu + ivodd is working on this.
d-i should have (beta or even better rc) releases
Do at least one DVD making dry run with the right installer, to ensure that everything fits properly.
Install Guide should be up-to-date
Task: https://lists.debian.org/debian-arm/2017/03/msg00022.html (waiting for arm porters)
ReleaseNotes need to be updated:
?KernelTeam signoff for specials with the Kernel
d-i team signoff for specials with this update (check esp. if old versions of d-i should be purged if new versions enter $suite's d-i area)
Task: https://lists.debian.org/debian-doc/2017/03/msg00001.html and rest of the thread: add info about new network interface naming https://lists.debian.org/debian-doc/2017/03/msg00006.html (waiting for systemd/udev maintainers?)
Security Team signoff for lower supported packages
- jmm confirmed it was fine via IRC.
- [ ] Do an English review, preferably before the call for translations
- [ ] Coordinate with translators
- Task: nthykier will handle translation coordination (freeze one week before the release)
[ ] Install & upgrade tests should reveal no undocumented (release notes, install guide) surprises
- [ ] Task: #854554 - preferably a fix
- [ ] Task: #801564 - preferably a fix
- [ ] Task: #863367 - document (other variants may appear)
- [ ] Dedication, if any
Write it
Coordinate translations
Call for signatures, collate
- [ ] Make available to FTP, CD teams
Coordinate date with the FTP-Team
Have an FTP-master ready/notified/available 3 weeks before the Release
- [ ] Website:
- [ ] Have a patch ready for template/debian/release_info.wml to update the current release. This is to be deployed during the release.
Ensure the planned release date is on debian.org/releases and on release.debian.org
Task: Make installation-gude updatable on the website again (https://lists.debian.org/debian-www/2017/06/msg00005.html)
- [ ] Send the preparation mail.
[ ] Notify the Security Team of an upcoming Release
Notify the Debian CD team of an upcoming Release
Notify the DebianLive Team of an upcoming Release
- [ ] Notify the Mirror team of an upcoming Release
Notify the publicity team of an upcoming Release
Prepare press release
- [ ] coordinate with d-i team for text for d-i changes
- [ ] Prepare the wiki changes
During the actual Release
[ ] Mention things that are happening on IRC so the publicity team can relay to social media
- [ ] Check with the FTP-Masters
- d-i needs to be moved
- new win32-loader?
- cleanup of $codename-proposed-updates and $codename-security
- stable-updates needs its suite name hack updated to oldstable-updates
- dedication installed
- [ ] Check /srv/ftp-master.debian.org/ftp/dists/$codename/ChangeLog
- [ ] Check if /srv/ftp.debian.org/ftp/README was updated.
- [ ] Sign the release file
- [ ] Check that everything that should be released really was released
[ ] Notify debian-security@lists.debian.org as people tend to cry occassionally
- [ ] Notify the Publicity Team, that Release is done (tell them when the Release will be pushed out)
[ ] Notify the Debian CD Team that the Release is done
[ ] Notify the DebianLive Team that the Release is done
- [ ] Update the website
[ ] Publish the ReleaseNotes
[ ] Update the wiki (coordinated with ReleaseNotes's editor)
- [ ] Watch mailing-lists for abnormalities
- [ ] Backup/flush hint files.
- [ ] Update release.debian.org/{oldoldstable,oldstable,stable,testing} symlinks; create the new suite for testing as a copy of stable and edit
After the release
[ ] Notify Distrowatch; send a mail to distro@distrowatch.com
[ ] Notify LWN, slashdot, Hacker News, Reddit
[ ] Propose a tweet/dent on the #debian-publicity IRC channel
- [ ] Blog about release team experiences
- [ ] Bits from the release team mail
[ ] Update the Debian timeline
[ ] Notify derivatives about the release
[ ] Update all the places that hardcode suite names or codenames