--- xml/htdocs/proj/en/glep/glep-0042.html 2006/03/06 03:12:58 1.11 +++ xml/htdocs/proj/en/glep/glep-0042.html 2006/09/05 20:36:38 1.14 @@ -15,8 +15,8 @@ /* :Author: David Goodger :Contact: firstname.lastname@example.org -:date: $Date: 2006/03/06 03:12:58 $ -:version: $Revision: 1.11 $ +:date: $Date: 2006/09/05 20:36:38 $ +:version: $Revision: 1.14 $ :copyright: This stylesheet has been placed in the public domain. Default cascading style sheet for the PEP HTML output of Docutils. @@ -275,11 +275,13 @@
This GLEP proposes a new way of informing users about important updates and news related to the tree.
Although most package updates are clean and require little user action, occasionally an upgrade requires user intervention. Recent examples of the latter include the gcc-3.4 stabilisation on x86 and the mysql-4.1 @@ -362,7 +364,7 @@
An adequate solution must meet all of the following requirements:
News items are published and delivered to users as follows:
The following extensions to Portage are required:
These extensions are assumed during the following specification.
Each news item will have a unique identifier. This identifier will be in the form yyyy-mm-dd-short-name, where yyyy is the year (e.g. 2005), mm is the month (01 through 12) and dd is the day of the month @@ -473,7 +475,7 @@ 0-9, + (plus), - (hyphen) and _ (underscore).
Each news item will be represented by a directory whose name is the same as the news item's identifier.
The directory will contain a file named yyyy-mm-dd-short-name.en.txt, which @@ -485,7 +487,7 @@ justified by precedent .
The following headers describe the purpose and format of the news item:
The header section must be followed by a blank line, then the main body of the text.
The text body should be wrapped at 72 characters. No fancy formatting or tab @@ -582,13 +584,13 @@ administrated — this will be the case on many servers and routers, for example.
There have been complaints regarding the comprehensibility of some upgrade notices and news items in the past. This is understandable — not every Gentoo developer speaks English as a first language. However, for the sake of clarity, @@ -612,9 +614,9 @@
News items are to be made available via the standard rsync tree. This removes any need for polling of a remote source.
A new repository will be created for news items. The type (CVS or Subversion), @@ -639,7 +641,7 @@ directory.
Once a news item is marked for reading, third party tools (or traditional core Unix tools) can be used to display and view the news files.
When a news item is read, its name should be removed from the @@ -688,7 +690,7 @@ desire them.
News items can be removed (by removing the news file from the main tree) when they are no longer relevant, if they are made obsolete by a future news item or after a long period of time. This is the same as the method used for updates @@ -696,39 +698,41 @@
It would be simple to convert these news items into the format used for news items on the Gentoo website or posts for the gentoo-announce mailing list.
There is an existing automated tool  for posting GLSAs to the forums. A similar tool can be used for these news items.
Backwards compatibility is not a concern here. Existing tools will simply ignore the news/ directory.
The idea behind notifying users of news updates via Portage comes from Stuart -Herbert .+Herbert .
Thanks to Lance Albertson, Stephen Bennett, Donnie Berkholz, Grant Goodyear, Brian Harring, Marius Mauch, Dan Meltzer, Jason Stubbs, Paul de Vrieze and Alec Warner for input. Some of the ideas presented here are theirs, others go completely against their suggestions.
|||Paludis homepage, http://paludis.berlios.de|
|||"Favouring an automatic news mechanism", Stuart Herbert, +|
|||"Favouring an automatic news mechanism", Stuart Herbert, http://stu.gnqs.org/diary/gentoo.php/2005/10/28/favouring_an_automatic_news_mechanism|