We plan to release an inofficial sarge-amd64 shortly after sarge
(allow for a final sync and check that everything is fine, create CDs,
DVDs, ...).
Great. I don't mind it being released a bit later than the official sarge. Obviously it would be great to see AMD64 being an officially supported architecture with sarge, but I don't see that comming.
It is also planed to do security support, by whom is not yet clear as noone has steped up for it yet.
Well, if a non-DD (as of now, I haven't been assigned to an AM) can help there, let me know.
> I also think "etch" will
be added at the same time sarge goes stable.
You mean etch/AMD64? Fine ;-)
Then, when sarge is out of the way, the new mirroring should get implemented by Debian alowing mirrors to drop unimportant archs and making space for amd64 to be added. Once that happens Debian will have an official etch and sid amd64 and those two will fade from alioth then, leaving only sarge and security there.
Well, that is the plan anyway.
Let's hope it goes well.
What happens to the gcc-3.4/gcc-4.0 repository is totaly undecided and I leave that up to Andreas as he is doing all the work on it.
Sure. To me that repository isn't very tempting since it (currently) is pretty far away from official sarge. Aside from that I think the gcc-3.4/gcc-4.0 repo is fine work and a necessary step in the direction of making gcc-3.4 or gcc-4.0 the official compiler suite for the main archive. There should probably similar repos for non-AMD64 arches though.
cu, sven
