| 1 |
Hi all, |
| 2 |
Its that time again :) While you are relaxing and hopefully sitting by |
| 3 |
the sun, I have been working on 2004.2 (and relaxing as well ;) |
| 4 |
|
| 5 |
Before I get to 2004.2, we need a 2004.1 recap. 2004.1 did amazingly |
| 6 |
well. In my time at Gentoo, I have never seen a release go so well. What |
| 7 |
we did for 2004.1 was truly amazing work - each of you should be proud |
| 8 |
as hell about what we got accomplished in that short amount of time. |
| 9 |
Everyone involved did a hell of a job, thank you :) |
| 10 |
|
| 11 |
Of course though, there are always things to improve. Here is what I see |
| 12 |
as areas that we could improve in: |
| 13 |
|
| 14 |
1. More QA on everything, especially LiveCDs |
| 15 |
2. Hardware detection and module autoloading for x86 |
| 16 |
3. Genkernel and initrds for other arches |
| 17 |
4. Better communication about what arches are releasing |
| 18 |
5. Deadline completion |
| 19 |
|
| 20 |
Okay, so here is the breakdown: |
| 21 |
|
| 22 |
To address #1 I have built a month+ of QA time into 2004.2 (please see |
| 23 |
the link at the bottom for the link to the preliminary 2004.2 page). A |
| 24 |
month of QA should allow us plenty of time to test everything that we |
| 25 |
have and fix whatever problems come up. Additionally, this extended QA |
| 26 |
period helps to fix #5, the more time we have on QA, the more likely we |
| 27 |
are to hit deadline because we won't have to hack in any last minute |
| 28 |
changes. Now, because of this month+ of QA, when the deadline rolls |
| 29 |
around, I am going to strictly adhere to it, so just keep that in mind. |
| 30 |
|
| 31 |
#2 is something that we are working on presently (we being beejay, |
| 32 |
roger55, and myself). This will probably go on the feature request list |
| 33 |
and get itself resolved rather quickly. |
| 34 |
|
| 35 |
#3 is all plasmaroo and the genkernel team. Please contact him ASAP with |
| 36 |
your bugs - he is lightning quick about patches to fix problems :) |
| 37 |
|
| 38 |
#4 is something pretty easy to address - please keep me up-to-date as to |
| 39 |
whether or not your arch can make it. This is not really a biggie, but |
| 40 |
it helps with planning. |
| 41 |
|
| 42 |
#5 will be fixed with #1, QA helps a lot of things :) |
| 43 |
|
| 44 |
The two areas of improvement that I expect will take the most time are |
| 45 |
#2 and #5. The extended QA period should help us here though. |
| 46 |
|
| 47 |
Okay, the schedule for 2004.2 is much more lax than 2004.1. Please take |
| 48 |
the time to look over the 2004.2 info sheet linked from the bottom of |
| 49 |
this mail and provide me with some feedback with regard to the schedule. |
| 50 |
Again, I want to make this release as low stress as possible, so let me |
| 51 |
know if I can adjust the schedule in any way to help complete this goal |
| 52 |
:) |
| 53 |
|
| 54 |
Ok, the last thing in this long e-mail (I swear :) is the feature |
| 55 |
request. Please see the mail that I am going to send to -core and -dev. |
| 56 |
Basically, I am going to field some feature requests and then hold a |
| 57 |
meeting with all of you on releng to see what requested features are |
| 58 |
feasible. I will keep you posted. |
| 59 |
|
| 60 |
Again, awesome job on 2004.1! Let's do the same and even more with |
| 61 |
2004.2. |
| 62 |
|
| 63 |
Cheers, |
| 64 |
//zhen |
| 65 |
|
| 66 |
Link to the 2004.2 page: |
| 67 |
http://nue.gentoo.org/proj/en/releng/release/2004.2/2004.2.xml |
| 68 |
|
| 69 |
-- |
| 70 |
John Davis |
| 71 |
Gentoo Linux Developer |
| 72 |
<http://dev.gentoo.org/~zhen> |
| 73 |
|
| 74 |
---- |
| 75 |
GnuPG Public Key: <http://dev.gentoo.org/~zhen/zhen_pub.asc> |
| 76 |
Fingerprint: 2364 71BD 4BC2 705D F338 FF70 6650 1235 1946 2D47 |
Archives