| 1 |
On Mon, Jun 23, 2003 at 08:22:11AM +0200, Philippe Lafoucrière wrote: |
| 2 |
> I was reading the new newsletter, especially the part : "Releases do not |
| 3 |
> matter in Gentoo Linux.".If releases really doesn't matter, why 1.4 |
| 4 |
> isn't out ? I DO know you can use a 1.4RC1/2/3/4 live cd have an up to |
| 5 |
> date system with emerge -u, but newbies don't. |
| 6 |
|
| 7 |
Bringing out a final version (1.4 in this case) is more than just telling |
| 8 |
people it's okay to use this version. It is also an event that will get |
| 9 |
noticed by other parties, not only distrowatch, linuxtoday and other |
| 10 |
newssites, but also LUGs and companies. |
| 11 |
|
| 12 |
Therefor a 1.4-release should be a milestone with certain criteria in mind. |
| 13 |
One of them (which I take very seriously) is documentation: you cannot |
| 14 |
release a final version without having all documentation ready. The same goes |
| 15 |
for the translations. |
| 16 |
|
| 17 |
Another one are the milestone-targets that were made public some weeks ago: |
| 18 |
* Baselayout independent of tmpfs |
| 19 |
* CFLAGS documentation or a tool that gives CFLAGS-building |
| 20 |
functionality |
| 21 |
* GRP creation and testing |
| 22 |
* Kernelscript to help ppl configure their kernel |
| 23 |
|
| 24 |
Most of those demands have been met, but GRP still needs some testing |
| 25 |
(correct me if I am wrong). |
| 26 |
|
| 27 |
Also, the LiveCD should work with as many configurations as possible. If you |
| 28 |
check bugs.gentoo.org for the term "livecd" you'll see that there are still |
| 29 |
bugs to be addressed. |
| 30 |
|
| 31 |
Avenj (Gentoo Release Coordinator), seemant (Development Manager) and |
| 32 |
drobbins (Chief Architect) should _all_ be able to sleep tight when |
| 33 |
the release is made. If one of them isn't sure about something, then the |
| 34 |
release should be delayed. |
| 35 |
|
| 36 |
Wkr, |
| 37 |
Sven Vermeulen |
| 38 |
Gentoo Documentation |
| 39 |
Dutch Translations |
| 40 |
-- |
| 41 |
Thanks to DRM, you know that something has been built in environment of |
| 42 |
unspecified degree of security, from source you cannot check, written by |
| 43 |
programmers you don't know, released after passing QA of unknown quality and |
| 44 |
which is released under a license that disclaims any responsibility... |
Archives