Mageia 2 RC a bit delayed

[ennael]

Hi there

http://blog.mageia.org/en/2012/05/02/ma ... good-wine/

And no, we did not drink anything during tests
RC should be out in a few days.

Cheers

[atleeit]

i'm waiting hard as for this nice RC update ....clicking fingers....tapping feet...head banging on wall -->D:|

[neograven]

I had asked this in the blog (not the best palce lol) but if I am using beta3 won't it automatically be updated to rc if I mark all updates?

[wobo]

Yes, of course. It will be updated continuously, that's Cauldron. Hint: When the final is released it will stay on Cauldron for the next version. So if you do not want this you have to switch from Cauldron to MGA2 final when the time comes (it will be announced).

Alpha 1-3, Beta 1-3 and RC are snapshots of Cauldron, taken at a scheduled time and serving to test the installer and isos at the respective stage.

[wilcal]

="wobo"Alpha 1-3, Beta 1-3 and RC are snapshots of Cauldron, taken at a scheduled time and serving to test the installer and isos at the respective stage.

To make a point, these prerelease versions are a capture of
Cauldron at a specific point in time and that published on
DVD and Live-CD ( isos ) and test the installer(s) on those
ISO's.

Released more often is the boot.iso file that uses the immediate
state of the repo ( be that Cauldron or a released version ). And
in fact installing using the boot.iso file will give you a mostly
up-to-date install as of the time that you run the install.

While I do ultimately burn and retain the final released DVD/Live-CD,
and do test the prerelease versions, I rely on the boot.iso for
ultimately doing my "production" installs.

[neograven]

Awesome, thanks a bunch!

[Ken-Bergen]

To make a point, these prerelease versions are a capture of
Cauldron at a specific point in time and that published on
DVD and Live-CD ( isos ) and test the installer(s) on those
ISO's.

Released more often is the boot.iso file that uses the immediate
state of the repo ( be that Cauldron or a released version ). And
in fact installing using the boot.iso file will give you a mostly
up-to-date install as of the time that you run the install.

While I do ultimately burn and retain the final released DVD/Live-CD,
and do test the prerelease versions, I rely on the boot.iso for
ultimately doing my "production" installs.

That's fine for a stable release but unless you're using a local mirror as you are it would likely fail with Cauldron.

Cauldron runs at a fast passe and even with a fast Internet connection it's possible/likely critical files will disappear and be replaced by newer versions during the installation resulting in a failed installation.

[wilcal]

That's fine for a stable release but unless you're using a local mirror as you are it would likely fail with Cauldron.

And I do run a local repo of both M1 and Cauldron and of course do
not let it update while I'm doing a test install with boot.iso

Cauldron runs at a fast passe and even with a fast Internet connection it's possible/likely critical files will disappear and be replaced by newer versions during the installation resulting in a failed installation.

I agree with that but if you pick a time less likely to be
when the Cauldron repo is updating your likely to be
successful. I live out here in the land of Crazies ( California )
and we're 9 hours time shifted. So if I'd do an install at say
in the afternoon then likely the Cauldron repo is pretty quite.
I've run into a problem like this a couple times with Mandriva
Cooker but rarely.