< Project:RelEng < LiveCD
Project:RelEng/LiveCD/2008.0
This document serves as the definitive source for the 2008.0 release.
Contacts
- Release Operations: Chris Gianelloni
- Documentation: Joshua Saddler
- Infrastructure: Robin H. Johnson
- Public Relations: Donnie Berkholz
- Security: Peter Volkov
Release schedule
Note
This schedule is tentative in nature and may change without notice based on the needs of the Release Engineering project and Gentoo, as a whole.
This schedule is tentative in nature and may change without notice based on the needs of the Release Engineering project and Gentoo, as a whole.
| Milestone | Target date | Description | Status |
|---|---|---|---|
| Initial meeting | 23 Jan 2008 | Plan release schedule, initial features, and other pertinent information for the upcoming release. A feature request is called after this meeting. | Completed |
| Feature request cut-off | 30 Jan 2008 | This is the cut-off date for feature requests. No feature requests will be honored after this date, to give ample time for QA. | Completed |
| Initial snapshot | 1 Feb 2008 | A snapshot is made from the tree which is used for building the release. After this point, packages are added/updated in the snapshot only if it is necessary due to the potential impact of the issue, such as security bugs, or release-specific changes, such as an updated livecd-tools. | Completed |
| QA builds/testing | 25 Feb 2008 | Several builds of the release media are made on each architecture, with modifications being made to the snapshot and the release building tools, as necessary. | Completed |
| Doc updates | 25 Feb 2008 | All documentation updates are to be submitted to the Documentation Liaison by this date for the upcoming release. Things that are commonly updated are the kernel versions used, kernel command line options that have been added/removed, and changes to the installation process. | Completed |
| Handbook updated | 29 Mar 2008 | The updated Handbook tarballs for each architecture are due to be delivered to Release Engineering for use on the Beta release. | Completed |
| Snapshot freeze (Beta 1) | 31 Mar 2008 | The snapshot is frozen to build an initial Beta release for wider testing in the community. Once the Beta is released, the snapshot is unfrozen. | Completed |
| Beta 1 information | 30 Mar 2008 | The press release/news item for the Beta release is written and has been submitted to Release Engineering for approval. | Completed |
| Beta 1 upload | 30 Mar 2008 | The Beta is uploaded to the release staging server for distribution under the experimental directory on participating mirrors. | Completed |
| Beta 1 release | 1 Apr 2008 | The Beta is publicly released. The front page is updated to reflect this and notification is sent to news outlets. | Completed |
| Snapshot freeze (Beta 2) | 23 Apr 2008 | The snapshot is frozen to build the second Beta release for wider testing in the community. Once the Beta is released, the snapshot is unfrozen. | Completed |
| Beta 2 information | 28 Apr 2008 | The press release/news item for the Beta release is written and has been submitted to Release Engineering for approval. | Completed |
| Beta 2 upload | 28 Apr 2008 | The Beta is uploaded to the release staging server for distribution under the experimental directory on participating mirrors. | Completed |
| Beta 2 release | 29 Apr 2008 | The Beta is publicly released. The front page is updated to reflect this and notification is sent to news outlets. | Completed |
| Snapshot freeze (Final) | 18 Jun 2008 | This is the due date for the final snapshot. After this point, no updates are made to the snapshot and the final build phase begins. | Completed |
| Doc updates | 18 Jun 2008 | Any additional changes to the Handbook must be submitted by this date. This coincides with the snapshot freeze, so no changes will happen in the snapshot past this date to ensure the accuracy of the Handbook. | Completed |
| Handbook updated | 19 Jun 2008 | The updated Handbook tarballs for each architecture are due to be delivered to Release Engineering for use on the final release. | Completed |
| Media uploaded | 04 Jul 2008 | All release media is uploaded to the release staging server (poseidon) by this date to be prepared for release. | Completed |
| Final preparation | 05 Jul 2008 | One final check is made of all release materials, DIGESTS files are signed, and any additional tasks are completed. | Completed |
| Release handover | 05 Jul 2008 | Release Engineering makes one final check of all materials, then hands it over to Infrastructure for staging and release. | Completed |
| Release | 06 Jul 2008 | All news items are committed, the release materials and Handbook are made visible to the public, and Release Engineering takes a well-deserved break. | Completed |
Architectures releasing
The following supported architectures are tentatively releasing 2008.0 media.
Note
The listing of supported architectures can be located in the Gentoo Linux Vulnerability Treatment Policy document maintained by the Gentoo Security team.
The listing of supported architectures can be located in the Gentoo Linux Vulnerability Treatment Policy document maintained by the Gentoo Security team.
| Architecture | Expected components | Release coordinator(s) |
|---|---|---|
| alpha | Minimal InstallCD, stages | Tobias Klausmann |
| amd64 | Minimal InstallCD, LiveCD, stages | Christoph Mende |
| hppa | Minimal InstallCD, Universal InstallCD, stages | Tobias Scherbaum |
| ppc | Minimal InstallCD, Universal InstallCD, stages | Brent Baude |
| sparc | Minimal InstallCD, Universal InstallCD, stages | Raúl Porcel |
| x86 | Minimal InstallCD, LiveCD, stages | Andrew Gaffney |
The following unsupported architectures are tentatively releasing 2008.0 media.
| Architecture | Expected components | Release coordinator(s) |
|---|---|---|
| arm | stages | Mike Frysinger |
| ia64 | Minimal InstallCD, stages | Raúl Porcel |
| mips | stages, netboot images | Stuart Longland |
| s390 | stages | Mike Frysinger |
If information regarding a specific architecture is wrong or has been omitted, please contact the release operations manager.
Release verification
Integrity checking
There will be DIGESTS files for all release media on the Gentoo mirrors. This file can be used to verify that the media that was downloaded was not corrupted in transit.
Source verification
All release media will have its DIGESTS file signed by the Gentoo Linux Release Engineering (releng@gentoo.org) PGP key. The public key ID is 0x17072058, and the key is available through the subkeys.pgp.net keyserver. This can be used to verify that the media is, in fact, the media shipped by Release Engineering and not from a potential attacker.
Release resources
Repositories
- svn+ssh://poseidon.amd64.dev.gentoo.org/release/repos/snapshot-tree (Read/Write, RelEng-only)
- svn+ssh://svn.gentoo.org/var/svnroot/releng (Read/Write, RelEng-only)
- svn://anonsvn.gentoo.org/releng (Read-only, public)
Note
There is no public repository for the snapshot. This is to keep the load down on our public SVN servers. The repository will be published after the release is completed.
There is no public repository for the snapshot. This is to keep the load down on our public SVN servers. The repository will be published after the release is completed.
This page is based on a document formerly found on our main website gentoo.org.
The following people contributed to the original document: Chris Gianelloni (author, July 6, 2008)
They are listed here because wiki history does not allow for any external attribution. If you edit the wiki article, please do not add yourself here; your contributions are recorded on each article's associated history page.
This article is issued from Gentoo. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.