Ok, so I will have to promote to the update site but leave the old artifacts.jar and contents.jar there until the final release date (so the new release artifacts remain invisible until then but the mirrors can do their job), right? Well, this means that in order to assure correct handling of the p2.mirrorsURL property in my publish script I will have to tweak the existing artifacts.jar of our current releases update-site manually (as no other repo is mirrored) and perform the tests with it (i.e. using the 3.7.2 release artifacts). And then let's hope that my publish script (which uses the WTP addRepoProperties application) behaves the same....
Cheers Alexander Am 19.06.2012 um 15:53 schrieb Denis Roy: > On 06/19/2012 08:18 AM, Alexander Nyßen wrote: >> >> Will it do any harm if I publish the release (which is anyhow promoted as >> RC4 on the milestones update-site) to the releases update-site in advance? > > I can only speak from the infrastructure perspective. > > As I type this, 18 mirrors (our configured limit) are connected and pulling > in the final bits for some projects. As you can suspect, these mirrors draw > a noticeable amount of bandwidth. As more projects move their files in their > final locations, our 50-or-so mirrors will be picking up the changes, and > we'll be under some strain for the rest of the week. That's why we call this > "quiet week". > > If some projects start publishing actual release bits, then we must also deal > with the added pain of supporting these user downloads. Since the mirrors > are not fully caught up, download.eclipse.org will be the only server > available. This will lead to congestion and grumpy users. > > Don't underestimate the amount of users who "Check for updates" just out of > curiosity. It's also no secret that Eclipse has a big release "sometime > towards the end of June" so as the days go by, anxious users get increasingly > click-happy. > > Back in the old days we didn't have a sync period, and releases where quite > chaotic. > > Denis > > > >> >> Cheers, >> Alexander >> -- >> Dr. Alexander Nyßen >> Dipl.-Inform. >> Software-Engineer >> >> Telefon: +49 (0) 231 / 98 60-210 >> Telefax: +49 (0) 231 / 98 60-211 >> Mobil: +49 (0) 151 / 17396743 >> >> http://www.itemis.de >> [email protected] >> >> itemis AG >> Am Brambusch 15-24 >> 44536 Lünen >> >> Rechtlicher Hinweis: >> >> Amtsgericht Dortmund, HRB 20621 >> >> Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens >> Trompeter, Sebastian Neus >> >> Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus >> >> >> >> >> _______________________________________________ >> cross-project-issues-dev mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Dr. Alexander Nyßen Dipl.-Inform. Software-Engineer Telefon: +49 (0) 231 / 98 60-210 Telefax: +49 (0) 231 / 98 60-211 Mobil: +49 (0) 151 / 17396743 http://www.itemis.de [email protected] itemis AG Am Brambusch 15-24 44536 Lünen Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
