It depends a little. But the safest thing
to do is leave RC4 in place until 6/27 (or, maybe remove 6/26, Tuesday,
one day, before release) and leave aggregator file pointing to it, RC4.
Then on 6/27, release becomes visible
and aggregator file can be updated then to point to final release location.
In my experience, some users will still
be trying to access RC4 stuff even this week and next, even knowing that
the release is next Wednesday ... so, besides aggregation concerns, best
not to leave your users empty handed. (and, main release location should
be "invisible" to them until 6/27.
We always say "no rebuilds for
any reason, at all, ever" after Monday 5 PM, so ... it is "ok"
if the aggregator files are broken for a day or two next week.
Of course, it would take an act of ...
someone very powerful ... to do a rebuild even now so if you break aggregation
files now, I doubt anyone would notice :).
Then, its just between you and your
I'm sure there's many variations on
these theme others have found that works for them, but I think the above
it good blend of "safety" and "efficiency".
Mark Russell <mrrussell@xxxxxxxxxx>
David M Williams/Raleigh/IBM@IBMUS,
06/20/2012 10:34 AM