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

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

Hi Andrew,

My idea was copy the bits to my project's site, test it there,
And then just rename the site.xml / p2 *.jar files such that
The site is not accessible.

This will allow contents to be mirrored, and I can just 
Rename back the "index" files on the release day, they
Should be mirrored quickly since they are small.

But perhaps somebody has a better or more elaborate way
Of doing this...

Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
direct +43.662.457915.85  fax +43.662.457915.6

-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx
[mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of
Andrew Overholt
Sent: Friday, June 04, 2010 3:47 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Helios Final Daze

Hi,

>     http://wiki.eclipse.org/Helios/Final_Daze

I read this over.  Thanks for writing it all up, Denis.  I have two
questions about staging the release and then making it go live on
release day.

The Linux Tools update site is:

  http://download.eclipse.org/technology/linuxtools/update/

Where do I put the bits such that they aren't available at that URL
before release day but are still mirrored and will be served by mirrors
from that URL after the release is available?

The same goes for the zips of our release.

Thanks,

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