Future of Ac... or even of PLD - update process

[Marcin Król]

> Let's just see. If there is not enough human-power for updating AC there will 
> be nothing we could do about it.
> 
> In case there is some update-powers what is your proposition/rule of process 
> of making updates in Ac ?
> 1. Commit, 
> 2. STBR (in commit log enough ? , or send directly to pld-devel ? , or to 
> given power-admins of Ac ) ?

Commit, mail directly to me or other developers with power to STBR.

> 3. If build success FTP-move to test / ready ? when to ac-updates ? When there 
> will be confimations of stuff working from users ?

First build should be sent to test to see if it will compile. Thats a
good place for people who want to test new versions. Anyone can send to
test.

When it will build on all architectures it should be sent to ready. It
will be kept there for at least 48 hours and then it will be moved to
main. Just like in Ra times.

> Thats looks more like not-so-fresh-Th than Ac-update. ;)  

Yes. Indeed. The only difference would be in fact gcc. Stable release
4.1 in Ac, unstable 4.2 snapshots in Th.

M.