On Tue, Jan 20, 2009 at 4:03 AM, Pierre Schmitz wrote:

Am Dienstag 20 Januar 2009 10:48:08 schrieb Gerhard Brauer:

...

Again: i wan't 2009.01 released latest this friday. Do you (or the Devs) see anything against this?

Btw: the new kenerl is already in core; but yes, we should ask all devs to stop psuhing new things to core until the iso is ready.

From my experience I would suggest the following:

* prepare an announcment/changelog * build and test the isos * Upload them till tomorrow * create torrents (I could do that) * Announce on friday (but make sure the isos are available on a majority of our mirrors)

I'm building the i686 ISOs right now. I will upload to gerolde in my home dir and give them to the private dev list for a quick beta test. When those are done, I will build the x86_64 versions One question: should we add a release to the version number, in case we need to push out another ISO (due to major errors) before the end of the month? 2009.01-1 ?

Am Tue, 20 Jan 2009 13:17:37 -0600 schrieb Aaron Griffin :

On Tue, Jan 20, 2009 at 4:03 AM, Pierre Schmitz wrote:

...

Am Dienstag 20 Januar 2009 10:48:08 schrieb Gerhard Brauer:

...

Again: i wan't 2009.01 released latest this friday. Do you (or the Devs) see anything against this?

Btw: the new kenerl is already in core; but yes, we should ask all devs to stop psuhing new things to core until the iso is ready.

From my experience I would suggest the following:

* prepare an announcment/changelog * build and test the isos * Upload them till tomorrow * create torrents (I could do that) * Announce on friday (but make sure the isos are available on a majority of our mirrors)

I'm building the i686 ISOs right now. I will upload to gerolde in my home dir and give them to the private dev list for a quick beta test. When those are done, I will build the x86_64 versions

Aaron, would you make the announce of the Release Engineering Group and the current status? So that users see: we are working, the next iso release is near. We could also say: only stopper ATM is FS#12867 (USB). But AFAIK that bug must be not a total stopper for the ISOs, installation and rescue/maintenance should be possible. Also we could apply your mkinitcpio patch preventive. (This is a bug in [core] and will affect to users only after installation, but IMHO it don't belong to iso/installation process. We could place a hint in ISO announce that **after** the installation new users maybe could run in this bug - as our "old users" do...) Gerhard

Aaron Griffin wrote:

On Thu, Jan 22, 2009 at 5:27 AM, Gerhard Brauer wrote:

...

Aaron, would you make the announce of the Release Engineering Group and the current status? So that users see: we are working, the next iso release is near.

Announcement made about the team. I didn't add info regarding the current status, but I think some people may expect it 8)

...

We could also say: only stopper ATM is FS#12867 (USB). But AFAIK that bug must be not a total stopper for the ISOs, installation and rescue/maintenance should be possible. Also we could apply your mkinitcpio patch preventive.

New mkinitcpio is in testing. Also, an initscripts package I'd like to get on the ISO (Copyright year changed to 2009)

I will rebuild sample ISOs with three new packages I updated today: aif, initscripts, and mkinitcpio

Thanks Aaron! We have 35 members watching this list (see http://www.archlinux.org/mailman/roster/arch-releng ) that's pretty cool! Aaron can you also set us up with write permissions to the developerwiki so we can start working on some documentation/procedures etc? Also, I couldn't find any release/installer related documentation on the current developerwiki, is there any documentation/drafts already written by others which could be useful to us? Dieter

On Thu, Jan 22, 2009 at 4:09 PM, Dieter Plaetinck wrote:

We have 35 members watching this list (see http://www.archlinux.org/mailman/roster/arch-releng ) that's pretty cool!

Woohoo!

Aaron can you also set us up with write permissions to the developerwiki so we can start working on some documentation/procedures etc? Also, I couldn't find any release/installer related documentation on the current developerwiki, is there any documentation/drafts already written by others which could be useful to us?

Done. Just try not to fiddle with the other docs related to packaging and the like 8)