Dan Price wrote:
On Tue 30 May 2006 at 12:59PM, Richard Lowe wrote:
Dan Price wrote:
On Tue 30 May 2006 at 03:36AM, Roland Mainz wrote:
Derek Cicero wrote:
We need to do little housecleaning on the download server, so going
forward our plan is to provide the following archival downloads:
+ For numbered builds we will keep the last 6 months.
Is it possible to extend that to 12 months, please ?
Some of the larger projects may have to wait longer for their inclusion
into OS/Net and IMO it may be bad if the original B[1-9][1-9] build
tools, sources etc. go away shortly before the putback just because
they're slightly over the six-month barrier...
[I agree with Casper: project gates should stay in sync...]
In the interest of historical curiousity, it seems like we might want to
something more phased:
- All builds for the past 6 months will be preserved
- Every 5th build for the past two years will be preserved.
- The first and last build of any given release will be
preserved in perpetuity.
Would that work? That would mean that someone would always have the
means to make a meaningful comparison between say, build 1 and build 70.
When an SCM arrives, this becomes largely academic, you'd be able to get
at any specific build (or individual putback) via the SCM. You can
recreate the tools from that specific tree. The only thing that *may*
pose a barrier would be the closed-bins, where applicable.
I don't think it's unreasonable for anyone wanting access to historic
moment-in-time trees to do so via the SCM, rather than a cycling set of
archived builds, and a few perpetually present builds.
It's somewhere between infeasible and you'd-rather-kill-yourself-instead
painful to do this with teamware as we use it today, so perhaps that's
my teamware-centric view of the world showing through.
With Mercurial:
hg up <revision or tag> # to bring your existing workspace 'back in
time'
hg clone -r <revision or tag> onnv-clone onnv-somebuild # to clone a
fresh, but historic workspace.
But I think it'd also be nice to keep the BFU archives, etc. around
according to some policy.
I hadn't considered the archives (I don't tend to use them), but I do
agree they could come in useful for pinpointing when a problem was
introduced, and similar things.
-- Rich.
_______________________________________________
opensolaris-discuss mailing list
[email protected]
