http://download.eclipse.org/releases/maintenance/
(Final EPP packages, I'm sure, will be ready tomorrow, Thursday is EPP
day).
Now even though it sounds like we are done, it is not the time to slack off
on testing! Time for final testing and preparation for downloads and
updates.
Besides testing stand alone packages, and the maintenance repo alone, be
sure to test update scenarios. For some guidance on how to do that, see
http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What.27s_the_best_way_to_test_with_the_staging_repository.3F
Remember our actual GA/Release day is Friday 2/24, and part of what that
means is projects should not announce our SR2 release is ready ... that
is, until our _simultaneous_ release on 2/24. (Naturally, you need to let
adopters know where to get the final bits, etc., but please avoid
announcing to general public that all is done ... if you do, there are
sometimes problems with users reporting I tried updating such and such to
SR2, but it failed because something else was out of sync).
But, you may say, 2/24 is over a week away, what if we find another bug we
want to fix? There's a FAQ for that:
http://wiki.eclipse.org/SimRel/Simultaneous_Release_FAQ#What_if_we_need_a_rebuild.2C_past_our_deadline.3F
(in short, prepare a patch :) justifications for a complete rebuild of the
whole stack are rare ... but, ask, after reading the FAQ, if you think you
have such a case).
Don't forget to clean up old releases, etc., as outlined in
http://wiki.eclipse.org/Indigo/Final_Daze
And, one thing I myself just now remembered, re-reading Final Daze, is
that some of you may need to update the Info Center, if your help
documents have changed for SR2.
I suggest continuing to use bug 348355
https://bugs.eclipse.org/bugs/show_bug.cgi?id=348355
If any other questions, don't hesitate to ask.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
