Re: [cross-project-issues-dev] Helios Final Daze

[Kim Moir <Kim_Moir@xxxxxxxxxx>]

To avoid users from updating before
the release day, this is what I do

1) Copy the release repository to the
release directory.
2)  Don't update the compositeContent.jar
or compositeArtifacts.jar to point to the child repository with the release
artifacts and metadata until the day of the release.  This allows
the artifacts to propagate to the mirrors without making them available
to users and causing traffic jams at eclipse.org.

If you don't use composite repos, delay
copying the content.jar and artifacts.jar to the release repo until we
know the mirrors are ready.

Kim

Andrew Overholt <overholt@xxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

06/04/2010 10:47 AM

Please respond to
Andrew Overholt <overholt@xxxxxxxxxx>; Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

To	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
cc
Subject	Re: [cross-project-issues-dev] Helios Final Daze

* Denis Roy <denis.roy@xxxxxxxxxxx> [2010-06-04
10:45]:
> You put them in their final resting place...  You just don't
publish
> links on web pages (or make release announcements) until the next
> day.

Oh, okay.  Users who have our previous release and hit "check
for
updates" will see them.  I assume that's okay?

Andrew
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev