On Mon, 2005-08-15 at 13:54 -0400, Jeffrey Forman wrote:
> Oh $diety, please let that be how it's done in the future. If I am still
> around and haven't lost my mind, this is how it should be done. A clean
> handoff from releng -> infra is what is needed so that we arent in any
> confusion about who's doing what...
Absolutely.
Also, I think we need to impose a policy on updates to things
in /releases. Over the past two releases, we've had things that got
updated on /releases without doing any sort of renaming of the files. I
think this causes bugs and confusion for our users. Instead, we should
enact and enforce a policy that no two different files in /releases
should ever have the same name. It'll cause a bit more bandwidth usage
for the mirrors, as they won't be able to simply rsync differences in
the file, but it will also reduce headaches anyone might have.
Example: stage3-athlon-xp-2005.1.tar.bz2 would become
stage3-athlon-xp-2005.1-r1.tar.bz2
This would also help enforce the releng->infra hand-off, as we would
simply give you the new file, and you guys would push it out, along with
updating the bouncer. At the same time, we would *require* that any
such changes be given to the GDP for them to update their information.
Now, should infra (well, Jeff) take the point in coordinating changes,
as in commits of updates, with the GDP, as it will be determined by the
time things are pushed to the mirrors, or should that remain a task for
the releng leads?
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
signature.asc
Description: This is a digitally signed message part
|
