Every release, we provide a document about the details leading up to the final, official release. It is long and wordy a) because I wrote it :) and b) the long version is intended primarily for those new to this whole thing, and there are details in there that are intended to be educational, as wall as map out the plan for the final days.
https://wiki.eclipse.org/Mars/Final_Daze For the rest of you, those that are already very familiar with the process, the basics are below as reminders. For everyone, be sure to ask, if there are any questions. = = = = = For most committers (or, specifically, release engineers, or project leads) the following are the main steps. 1. Clean up old builds on downloads and move previous releases to archives site. 2. Provide data for Infocenter docs, for help.eclipse.org (bug 469456 ). 3. Put your final bits in their final resting places, with their final names, early -- during quiet week -- but do not advertise them or make "visible" to the world. Be sure to change, correct, or add metadata -- such as download.php mirror URLs -- so they are correct for final location and names. 4. On official release day, Wednesday, June 24, check cross-project list approximately 10 AM (Eastern) to make sure there is no "Wait! Stop ship!" message. Once you see a "Go" message, you're free to advertise your release and make visible to the world. (And, while your thinking of it, just as well update Foundation's metadata to change "planned" to "completed", etc. 5. Keep an eye open for a few hours to make sure no reports of "bad things are happening", but otherwise Blog, Tweet, Celebrate! = = = = = Thanks all!
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
