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 users/adopters. 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". HTH From: Mark Russell <mrruss...@google.com> To: David M Williams/Raleigh/IBM@IBMUS, Date: 06/20/2012 10:34 AM Subject: windowbuilder currently my aggrigation file points to http://download.eclipse.org/windowbuilder/WB/rc/4.2.0-201206121200-RC4/4.2 when Should I update it to point to http://download.eclipse.org/windowbuilder/WB/release/R201206261200/4.2 which is my release directory -- Mark R Russell (724) 473-3140 Software Engineer in Test Google Pittsburgh
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
