Draft for release policy pending feedback
"Frantz Dhin" <[email protected]> Sun, 31 Aug 2003 15:26:43 +0200
| Newsgroups | gmane.linux.zynot.devel |
|---|---|
| Message-ID | <000001c36fc3$854519b0$07d2a8c0@spacelab> |
This is a multi-part message in MIME format. --===============67807731274838834== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C36FD4.48CDE9B0" This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C36FD4.48CDE9B0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit This draft has been written by me after sporadic discussion in #zynot-dev. The way I see it it is a reasonable middle-ground between Debian and Gentoo with some of the quirks of each sorted out. Comments wanted. Zynot has a 9-12 months release cycle. The arch leads are release managers of each new version of Zynot. They maintain different release schedules for each arch. However, their effort is coordinated and major releases within each arch should not differ from the agreed release date by more than 1-2 months. The version numbers follow each other. One arch is not required to wait for another arch to be 100% done before releasing. The arch leaders gather on a meeting well in advance of a release and agree on which features to offer and which package versions to freeze for future release. As a result of these meetings, each arch leader maintains a roadmap towards release that is public. It should show dates for alphas, betas, release candidates planned as well as final release date. The version numbering should reflect to the consumer how well this release of Zynot will interoperate with earlier releases and how much of an advantage it is to upgrade. As we are not a desktop-centric distribution our policy on version numbers will differ from that of RedHat and Mandrake since these mainly follow the release cycle and version numbering of KDE and Gnome. The arch leaders identify a number of products that are relevant for Zynot to offer. This could be a Zynot workstation, a Zynot webserver, a Zynot database server, a Zynot development workstation and much more. All packages needed to offer each product are provided as binaries. Everything that runs on top such as irc clients, media players and office suites are offered as ebuilds only. Not all products will make sense on all arches. It is up to the arch leader to decide what should be offered within his arch. Preferably this should be decided based on community feedback and needs. The arch lead should note in his public roadmap which products will be offered. The binary packages are frozen. No version bumps will happen unless there is a new release of Zynot. The packages provided as ebuilds only can freely be updated by the maintainers at their leisure. Security updated binary packages are of course an exception from this rule. Zynot must support a migration path going 2 versions back. If Zynot has released a v1.0 and a v2.0 then upgrades to v3.0 from BOTH these version should be supported and painless. The lifecycle of v1.0 ends when v3.0 is released. We will then no longer offer security fixes or backports of these for v1.0. Thorough and well-tested documentation for "upgrading to Zynot vX.X" should be ready on the release date. The documentation must also, of course, go 2 versions back. Regards Frantz Dhin, President Zynot Foundation ------=_NextPart_000_0001_01C36FD4.48CDE9B0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dus-ascii"> <meta name=3DProgId content=3DWord.Document> <meta name=3DGenerator content=3D"Microsoft Word 10"> <meta name=3DOriginator content=3D"Microsoft Word 10"> <link rel=3DFile-List href=3D"cid:[email protected]"> <!--[if gte mso 9]><xml> <o:OfficeDocumentSettings> <o:DoNotRelyOnCSS/> </o:OfficeDocumentSettings> </xml><![endif]--><!--[if gte mso 9]><xml> <w:WordDocument> <w:SpellingState>Clean</w:SpellingState> <w:GrammarState>Clean</w:GrammarState> <w:DocumentKind>DocumentEmail</w:DocumentKind> <w:HyphenationZone>21</w:HyphenationZone> <w:EnvelopeVis/> <w:Compatibility> <w:BreakWrappedTables/> <w:SnapToGridInCell/> <w:WrapTextWithPunct/> <w:UseAsianBreakRules/> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> </w:WordDocument> </xml><![endif]--> <style> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline; text-underline:single;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline; text-underline:single;} p {mso-margin-top-alt:auto; margin-right:0cm; mso-margin-bottom-alt:auto; margin-left:0cm; mso-pagination:widow-orphan; font-size:12.0pt; font-family:"Times New Roman"; mso-fareast-font-family:"Times New Roman";} span.EmailStyle17 {mso-style-type:personal-compose; mso-style-noshow:yes; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt; font-family:Arial; mso-ascii-font-family:Arial; mso-hansi-font-family:Arial; mso-bidi-font-family:Arial; color:windowtext;} span.SpellE {mso-style-name:""; mso-spl-e:yes;} @page Section1 {size:595.3pt 841.9pt; margin:3.0cm 2.0cm 3.0cm 2.0cm; mso-header-margin:35.4pt; mso-footer-margin:35.4pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> </style> <!--[if gte mso 10]> <style> /* Style Definitions */=20 table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Times New Roman";} </style> <![endif]--> </head> <body lang=3DDA link=3Dblue vlink=3Dpurple = style=3D'tab-interval:65.2pt'> <div class=3DSection1> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>This draft has been = written by me after sporadic discussion in #<span class=3DSpellE>zynot</span>-dev. = The way I see it <span class=3DSpellE>it</span> is a reasonable middle-ground = between <span class=3DSpellE>Debian</span> and <span class=3DSpellE>Gentoo</span> with = some of the quirks of each sorted out. Comments = wanted.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><span class=3DSpellE><font size=3D3 face=3D"Times = New Roman"><span lang=3DEN-GB = style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>Zynot</span></font></s= pan><span lang=3DEN-GB style=3D'mso-ansi-language:EN-GB'> has a 9-12 months = release cycle.<o:p></o:p></span></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>The arch leads are = release managers of each new version of <span class=3DSpellE>Zynot</span>. They = maintain different release schedules for each arch. However, their effort is = coordinated and major releases within each arch should not differ from the agreed = release date by more than 1-2 months. The version numbers follow each other. One = arch is not required to wait for another arch to be 100% done before = releasing.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>The arch leaders = gather on a meeting well in advance of a release and agree on which features to = offer and which package versions to freeze for future release. As a result of = these meetings, each arch leader maintains a roadmap towards release that is = public. It should show dates for alphas, betas, release candidates planned as = well as final release date.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>The version numbering = should reflect to the consumer how well this release of <span = class=3DSpellE>Zynot</span> will interoperate with earlier releases and how much of an advantage it = is to upgrade. As we are not a desktop-centric distribution our policy on = version numbers will differ from that of <span class=3DSpellE>RedHat</span> and = Mandrake since these mainly follow the release cycle and version numbering of KDE = and Gnome.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>The arch leaders = identify a number of products that are relevant for <span = class=3DSpellE>Zynot</span> to offer. This could be a <span class=3DSpellE>Zynot</span> workstation, a = <span class=3DSpellE>Zynot</span> <span class=3DSpellE>webserver</span>, a = <span class=3DSpellE>Zynot</span> database server, a <span = class=3DSpellE>Zynot</span> development workstation and much more. All packages needed to offer each product are provided as binaries. Everything that runs on top such as = <span class=3DSpellE>irc</span> clients, media players and office suites are = offered as <span class=3DSpellE>ebuilds</span> only.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>Not all products will = make sense on all arches. It is up to the arch leader to decide what should = be offered within his arch. Preferably this should be decided based on = community feedback and needs. The arch lead should note in his public roadmap = which products will be offered.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>The binary packages = are frozen. No version bumps will happen unless there is a new release of = <span class=3DSpellE>Zynot</span>. The packages provided as <span = class=3DSpellE>ebuilds</span> only can freely be updated by the maintainers at their leisure. Security updated binary packages are of course an exception from this rule. = <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><span class=3DSpellE><font size=3D3 face=3D"Times = New Roman"><span lang=3DEN-GB = style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>Zynot</span></font></s= pan><span lang=3DEN-GB style=3D'mso-ansi-language:EN-GB'> must support a migration = path going 2 versions back. If <span class=3DSpellE>Zynot</span> has released a = v1.0 and a v2.0 then upgrades to v3.0 from BOTH these version should be supported = and painless. The lifecycle of v1.0 ends when v3.0 is released. We will then = no longer offer security fixes or <span class=3DSpellE>backports</span> of = these for v1.0. <o:p></o:p></span></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>Thorough and = well-tested documentation for “upgrading to <span class=3DSpellE>Zynot</span> = <span class=3DSpellE>vX.X</span>” should be ready on the release date. = The documentation must also, of course, go 2 versions = back.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'><o:p> </o:p></spa= n></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>Regards<o:p></o:p></sp= an></font></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = lang=3DEN-GB style=3D'font-size:12.0pt;mso-ansi-language:EN-GB'>Frantz <span = class=3DSpellE>Dhin</span>, President <span class=3DSpellE>Zynot</span> = Foundation<o:p></o:p></span></font></p> </div> </body> </html> ------=_NextPart_000_0001_01C36FD4.48CDE9B0-- --===============67807731274838834== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ zynot-dev mailing list [email protected] http://lists.zynot.org/mailman/listinfo/zynot-dev --===============67807731274838834==--