/[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.6 Revision 1.8
1GLEP: 19 1GLEP: 19
2Title: Gentoo Stable Portage Tree 2Title: Gentoo Stable Portage Tree
3Version: $Revision: 1.6 $ 3Version: $Revision: 1.8 $
4Last-Modified: $Date: 2004/11/02 15:38:58 $ 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: 29-Jan-2004 2-Nov-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
71stable 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,
72it 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
73number 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
74resource constrained and unable to meed future deadlines. 79resource constrained and unable to meed future deadlines.
75 80
76The 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
77"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
78"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.
79tree while "~stable" would be reserved for ebuilds which may be appropriate
80for the stable tree, but may require further testing before being deemed
81"ready for production". Off-cycle bug fixes and/or security updates may be
82examples of ebuilds that require the ~stable tag.
83 84
84Implementation 85Implementation
85============== 86==============
86 87
87While a 'stable' keyword was originally proposed, after further review, it was 88This GLEP will create a new set of cascaded profiles (one per release, not to
88determined this offered no way to allow arch-specific stable ebuilds. As 89exceed two per year) which will contain a subset of packages, including
89such, this GLEP proposes the use of 'stable:<arch>' and '~stable:<arch>' 90versions. This profile will "pin" a Gentoo Linux box to a specific set of
90(stable:x86, stable:ppc, etc.) 91packages and will only be updated for security updates and, in rare
92circumstances, major bug fixes.
91 93
92A new, stable tree will be created by scanning for the 'stable:<arch>' and 94Because this profile will be cascaded, the option exists for other developers
93'~stable:<arch>' keywords in the ebuilds and pulling those ebuilds and 95to create their own profile, containing a subset of packages not found in the
94associated files into a separate branch of CVS. The stable tree should have 96"main" stable tree and include those as part of the overall stable profile.
95the following features: 97These cases will be treated on a one-off basis.
96 98
97* Updated quarterly. Frozen during other times except for security/bug fixes 99The initial version will be x86 only, though other people will be encouraged
98* All ebuilds should remain in the tree for a minimum of one year. This 100to provide separate stable profiles for other arches. It is expected that any
99 allows users to upgrade as infrequently as once per year without risking 101effort to provide a stable tree for any arch or flavor of Gentoo will follow
100 the stable portage tree leaving them behind without an upgrade path. 102the basic outline of this GLEP to ensure consistency for our users.
101 103
102As mentioned above, the "stable" tree will be updated quarterly, ideally in 104In addition to a custom profile, this GLEP will also create a separate rsync
103unison with the release schedule of the main Gentoo branch. This tree will be 105repository, "gentoo-stable-portage", which will be available on all servers in
104untouched outside of this update schedule except in the following cases: 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.
105 111
106* Security fixes and patches which result in a GLSA 112Stable profiles will be maintained on an N - 2 basis. That is to say that we
107* Bug fixes for bugs ranked as 'maj' or above (may be overridden at the 113will maintain a stable profile for the most current release, plus the previous
108 discretion of the package maintainer.) 114two releases. With the expected release schedule for 2005, this will result
109 115in each profile being supported for approximately 18 months. Future versions
110In both cases, the maintainer of the package will be responsible for ensuring 116of the stable portage tree may seek to increase the life of these profiles.
111these patches are properly committed to the stable tree out of cycle.
112 117
113Backwards Compatibility 118Backwards Compatibility
114======================= 119=======================
115 120
116All 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.6  
changed lines
  Added in v.1.8

  ViewVC Help
Powered by ViewVC 1.1.20