/[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.1 Revision 1.4
1GLEP: 18 1GLEP: 19
2Title: Gentoo Bimonthly Publication 2Title: Gentoo Stable Portage Tree
3Version: $Revision: 1.1 $ 3Version: $Revision: 1.4 $
4Last-Modified: $Date: 2004/01/27 01:50:51 $ 4Last-Modified: $Date: 2004/01/30 02:41:45 $
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: 26-Jan-2004 10Post-History: 29-Jan-2004
11 11
12 12
13Abstract 13Abstract
14======== 14========
15 15
69resource constrained and unable to meed future deadlines. 69resource constrained and unable to meed future deadlines.
70 70
71The suggestion that seemed to get the most traction was the creation of a new 71The suggestion that seemed to get the most traction was the creation of a new
72"stable" keyword which would be added to appropriate ebuilds. The use of 72"stable" keyword which would be added to appropriate ebuilds. The use of
73"stable" would signify ebuilds that are ready for production in the stable 73"stable" would signify ebuilds that are ready for production in the stable
74tree whils "~stable" would be reserved for ebuilds which may be appropriate 74tree while "~stable" would be reserved for ebuilds which may be appropriate
75for the stable tree, but may require further testing before being deemed 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 76"ready for production". Off-cycle bug fixes and/or security updates may be
77examples of ebuilds that require the ~server tag. 77examples of ebuilds that require the ~server tag.
78 78
79Implementation 79Implementation
80============== 80==============
81 81
82While a 'stable' keyword was originally proposed, after further review, it was
83determined this offered no way to allow arch-specific stable ebuilds. As
84such, this GLEP proposes the use of 'stable:<arch>' and '~stable:<arch>'
85(stable:x86, stable:ppc, etc.)
86
82A new, stable tree will be created by scanning for the 'server' and '~server' 87A new, stable tree will be created by scanning for the 'stable:<arch>' and
83keywords in the ebuilds and pulling those ebuilds and associated files into a 88'~stable:<arch>' keywords in the ebuilds and pulling those ebuilds and
84separate branch of CVS. The stable tree should have the following features: 89associated files into a separate branch of CVS. The stable tree should have
90the following features:
85 91
86* Updated quarterly. Frozen during other times except for security/bug fixes 92* Updated quarterly. Frozen during other times except for security/bug fixes
87* All ebuilds should remain in the tree for a minimum of one year to ensure 93* All ebuilds should remain in the tree for a minimum of one year. This
88 that administrators will know how often their servers need to be upgraded 94 allows users to upgrade as infrequently as once per year without risking
95 the stable portage tree leaving them behind without an upgrade path.
89 96
90As mentioned above, the "stable" tree will be updated quarterly, ideally in 97As mentioned above, the "stable" tree will be updated quarterly, ideally in
91unison with the release schedule of the main Gentoo branch. This tree will be 98unison with the release schedule of the main Gentoo branch. This tree will be
92untouched outside of this update schedule except in the following cases: 99untouched outside of this update schedule except in the following cases:
93 100

Legend:
Removed from v.1.1  
changed lines
  Added in v.1.4

  ViewVC Help
Powered by ViewVC 1.1.20