/[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.2 Revision 1.8
1GLEP: 19 1GLEP: 19
2Title: Gentoo Stable Portage Tree 2Title: Gentoo Stable Portage Tree
3Version: $Revision: 1.2 $ 3Version: $Revision: 1.8 $
4Last-Modified: $Date: 2004/01/27 01:55:37 $ 4Last-Modified: $Date: 2006/10/10 16:54:34 $
5Author: Kurt Lieber <klieber@gentoo.org> 5Author: Kurt Lieber <klieber@gentoo.org>
6Status: Draft 6Status: Withdrawn
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: 26-Jan-2004 10Post-History: 29-Jan-2004 2-Nov-2004 7-Dec-2004 10-Oct-2006
11 11
12Status
13======
14
15Withdrawn by the author. "If someone wants to take up the torch, more
16power to them, but they should probably start clean with a new glep."
12 17
13Abstract 18Abstract
14======== 19========
15 20
16This GLEP is intended to propose a series of changes to the Portage tree that 21This GLEP is intended to propose a series of changes to the Portage tree that
20 25
21The proposed solution involves creating a separate tree in Portage that is 26The proposed solution involves creating a separate tree in Portage that is
22updated far less often than the regular tree. Outside of periodic updates, 27updated far less often than the regular tree. Outside of periodic updates,
23this tree would only be updated with critical bugfixes and security patches. 28this tree would only be updated with critical bugfixes and security patches.
24 29
30Status
31======
32
33Currently recruiting people who would be willing to help with this GLEP.
34
25Motivation 35Motivation
26========== 36==========
27 37
28Enterprise customers typically value stability and a predictable upgrade path 38Enterprise users typically value stability and a predictable upgrade path
29over having the latest packages or features available to them. Historically, 39over having the latest packages or features available to them. Historically,
30Gentoo Linux has been unable to provide such an environment due to the dynamic 40Gentoo Linux has been unable to provide such an environment due to the dynamic
31nature of the Portage tree. 41nature of the Portage tree.
32 42
33Specification 43Specification
66stable tree. While this might prove effective for a small number of ebuilds, 76stable 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 77it 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 78number of ebuilds in the stable tree and, over time, the project would become
69resource constrained and unable to meed future deadlines. 79resource constrained and unable to meed future deadlines.
70 80
71The suggestion that seemed to get the most traction was the creation of a new 81While 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 82keyword, 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 83profile, which will be used to track a subset of packages and versions.
74tree whils "~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 ~server tag.
78 84
79Implementation 85Implementation
80============== 86==============
81 87
82A new, stable tree will be created by scanning for the 'server' and '~server' 88This GLEP will create a new set of cascaded profiles (one per release, not to
83keywords in the ebuilds and pulling those ebuilds and associated files into a 89exceed two per year) which will contain a subset of packages, including
84separate branch of CVS. The stable tree should have the following features: 90versions. This profile will "pin" a Gentoo Linux box to a specific set of
91packages and will only be updated for security updates and, in rare
92circumstances, major bug fixes.
85 93
86* Updated quarterly. Frozen during other times except for security/bug fixes 94Because this profile will be cascaded, the option exists for other developers
87* All ebuilds should remain in the tree for a minimum of one year to ensure 95to create their own profile, containing a subset of packages not found in the
88 that administrators will know how often their servers need to be upgraded 96"main" stable tree and include those as part of the overall stable profile.
97These cases will be treated on a one-off basis.
89 98
90As mentioned above, the "stable" tree will be updated quarterly, ideally in 99The initial version will be x86 only, though other people will be encouraged
91unison with the release schedule of the main Gentoo branch. This tree will be 100to provide separate stable profiles for other arches. It is expected that any
92untouched outside of this update schedule except in the following cases: 101effort to provide a stable tree for any arch or flavor of Gentoo will follow
102the basic outline of this GLEP to ensure consistency for our users.
93 103
94* Security fixes and patches which result in a GLSA 104In addition to a custom profile, this GLEP will also create a separate rsync
95* Bug fixes for bugs ranked as 'maj' or above (may be overridden at the 105repository, "gentoo-stable-portage", which will be available on all servers in
96 discretion of the package maintainer.) 106the rsync.gentoo.org rotation. This repository will be *identical* to the
107main gentoo-portage repository except that the --delete flag will be removed
108from the rsync option that populates the tree. This will ensure that users of
109the stable profile will not have to worry about ebuilds for their packages
110disappearing.
97 111
98In both cases, the maintainer of the package will be responsible for ensuring 112Stable profiles will be maintained on an N - 2 basis. That is to say that we
99these patches are properly committed to the stable tree out of cycle. 113will maintain a stable profile for the most current release, plus the previous
114two releases. With the expected release schedule for 2005, this will result
115in each profile being supported for approximately 18 months. Future versions
116of the stable portage tree may seek to increase the life of these profiles.
100 117
101Backwards Compatibility 118Backwards Compatibility
102======================= 119=======================
103 120
104All features proposed here are new additions to existing processes and 121All features proposed here are new additions to existing processes and

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.8

  ViewVC Help
Powered by ViewVC 1.1.20