[1387] in athena10
Re: Apt repository layout
daemon@ATHENA.MIT.EDU (Mitchell E Berger)
Sun Mar 8 01:06:25 2009
Message-Id: <200903080605.n2865Pn0008196@byte-me.mit.edu>
To: Evan Broder <broder@MIT.EDU>
cc: debathena@MIT.EDU
In-Reply-To: Your message of "Sat, 07 Mar 2009 21:51:28 EST."
<49B332B0.5010806@mit.edu>
Date: Sun, 08 Mar 2009 01:05:25 -0500
From: Mitchell E Berger <mitchb@MIT.EDU>
Hey Evan,
> >> We should come up with some Moira clusterinfo settings to indicate that
> >> a machine should be using -proposed. We could possibly match the current
> >> sysprefix clusterinfo setting, but having a setting of our own seems
> >> like it might be a better long-term option.
> >>
> >>
> >
> > Do people mind if I request that we get the key "apt-release" added to
> > the public-linux, beta-linux, and alpha-linux clusters (with the value
> > of "production", "proposed", and "development", respectively)?
> >
>
> Hmm...I think I would actually ask for a "production" value in
> public-linux, entries with values of "proposed" and "production" for
> beta-linux, and entries with all 3 values for alpha-linux - it seems
> like a bad idea for the auto-updater to assume that one release implies
> another.
>
> I guess I should point out that such a change should have absolutely no
> effect on any non-Debathena systems. For that matter, it won't have any
> effect on Debathena systems yet.
No problem with what you propose above, but please also include the
addition of appropriate values to the early-linux cluster as well;
whether we migrate machines out of there to the other clusters or not,
people who had machines in early may well want to play with Debathena
before we hash out the plan, and they may as well have good Debathena
clusterinfo from the outset. Definitely production, definitely not
development, "meh" on proposed.
Mitch
