/[gentoo]/xml/htdocs/proj/en/glep/glep-0019.txt
Gentoo

Diff of /xml/htdocs/proj/en/glep/glep-0019.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.5 Revision 1.7
1GLEP: 19 1GLEP: 19
2Title: Gentoo Stable Portage Tree 2Title: Gentoo Stable Portage Tree
3Version: $Revision: 1.5 $ 3Version: $Revision: 1.7 $
4Last-Modified: $Date: 2004/02/02 18:16:31 $ 4Last-Modified: $Date: 2004/12/08 00:24:23 $
5Author: Kurt Lieber <klieber@gentoo.org> 5Author: Kurt Lieber <klieber@gentoo.org>
6Status: Draft 6Status: Draft
7Type: Standards Track 7Type: Standards Track
8Content-Type: text/x-rst 8Content-Type: text/x-rst
9Created: 26-Jan-2004 9Created: 26-Jan-2004
10Post-History: 29-Jan-2004 10Post-History: 29-Jan-2004 2-Nov-2004 7-Dec-2004
11 11
12 12
13Abstract 13Abstract
14======== 14========
15 15
19environments, mission critical workstations and other such installations. 19environments, mission critical workstations and other such installations.
20 20
21The proposed solution involves creating a separate tree in Portage that is 21The proposed solution involves creating a separate tree in Portage that is
22updated far less often than the regular tree. Outside of periodic updates, 22updated far less often than the regular tree. Outside of periodic updates,
23this tree would only be updated with critical bugfixes and security patches. 23this tree would only be updated with critical bugfixes and security patches.
24
25Status
26======
27
28Currently recruiting people who would be willing to help with this GLEP.
24 29
25Motivation 30Motivation
26========== 31==========
27 32
28Enterprise users typically value stability and a predictable upgrade path 33Enterprise users typically value stability and a predictable upgrade path
66stable tree. While this might prove effective for a small number of ebuilds, 71stable tree. While this might prove effective for a small number of ebuilds,
67it is quite likely that this model would not scale enough to allow for a large 72it is quite likely that this model would not scale enough to allow for a large
68number of ebuilds in the stable tree and, over time, the project would become 73number of ebuilds in the stable tree and, over time, the project would become
69resource constrained and unable to meed future deadlines. 74resource constrained and unable to meed future deadlines.
70 75
71The suggestion that seemed to get the most traction was the creation of a new 76While the original draft of this GLEP called for the creation of a stable
72"stable" keyword which would be added to appropriate ebuilds. The use of 77keyword, we have since discarded that idea in favor of creating a custom
73"stable" would signify ebuilds that are ready for production in the stable 78profile, which will be used to track a subset of packages and versions.
74tree while "~stable" would be reserved for ebuilds which may be appropriate
75for the stable tree, but may require further testing before being deemed
76"ready for production". Off-cycle bug fixes and/or security updates may be
77examples of ebuilds that require the ~stable tag.
78 79
79Implementation 80Implementation
80============== 81==============
81 82
82While a 'stable' keyword was originally proposed, after further review, it was 83This GLEP will create a new set of cascaded profiles (one per release, not to
83determined this offered no way to allow arch-specific stable ebuilds. As 84exceed two per year) which will contain a subset of packages, including
84such, this GLEP proposes the use of 'stable:<arch>' and '~stable:<arch>' 85versions. This profile will "pin" a Gentoo Linux box to a specific set of
85(stable:x86, stable:ppc, etc.) 86packages and will only be updated for security updates and, in rare
87circumstances, major bug fixes.
86 88
87A new, stable tree will be created by scanning for the 'stable:<arch>' and 89Because this profile will be cascaded, the option exists for other developers
88'~stable:<arch>' keywords in the ebuilds and pulling those ebuilds and 90to create their own profile, containing a subset of packages not found in the
89associated files into a separate branch of CVS. The stable tree should have 91"main" stable tree and include those as part of the overall stable profile.
90the following features: 92These cases will be treated on a one-off basis.
91 93
92* Updated quarterly. Frozen during other times except for security/bug fixes 94The initial version will be x86 only, though other people will be encouraged
93* All ebuilds should remain in the tree for a minimum of one year. This 95to provide separate stable profiles for other arches. It is expected that any
94 allows users to upgrade as infrequently as once per year without risking 96effort to provide a stable tree for any arch or flavor of Gentoo will follow
95 the stable portage tree leaving them behind without an upgrade path. 97the basic outline of this GLEP to ensure consistency for our users.
96 98
97As mentioned above, the "stable" tree will be updated quarterly, ideally in 99In addition to a custom profile, this GLEP will also create a separate rsync
98unison with the release schedule of the main Gentoo branch. This tree will be 100repository, "gentoo-stable-portage", which will be available on all servers in
99untouched outside of this update schedule except in the following cases: 101the rsync.gentoo.org rotation. This repository will be *identical* to the
102main gentoo-portage repository except that the --delete flag will be removed
103from the rsync option that populates the tree. This will ensure that users of
104the stable profile will not have to worry about ebuilds for their packages
105disappearing.
100 106
101* Security fixes and patches which result in a GLSA 107Stable profiles will be maintained on an N - 2 basis. That is to say that we
102* Bug fixes for bugs ranked as 'maj' or above (may be overridden at the 108will maintain a stable profile for the most current release, plus the previous
103 discretion of the package maintainer.) 109two releases. With the expected release schedule for 2005, this will result
104 110in each profile being supported for approximately 18 months. Future versions
105In both cases, the maintainer of the package will be responsible for ensuring 111of the stable portage tree may seek to increase the life of these profiles.
106these patches are properly committed to the stable tree out of cycle.
107 112
108Backwards Compatibility 113Backwards Compatibility
109======================= 114=======================
110 115
111All features proposed here are new additions to existing processes and 116All features proposed here are new additions to existing processes and

Legend:
Removed from v.1.5  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.20