Community
Participate
Working Groups
Many of the recent updates/abstractions to promotion scripts makes this much easier, but there is one last step that could be easily automated. Currently, all promotions are done with a "hidden" flag. We _have_ to do that with final releases, to coordinate, but I've found it a good thing to do even for milestones and release candidates. One advantage is it allows someone (i.e. me) to sanity check the pages and sites before the rest of the world sees them, and a second advantage is that even waiting a few hours can allow a few of the faster/larger mirrors to get copies which improves some initial downloads (though, its not always perfectly clear which are mirrored, and which are not). But, given that the "hidden flag" is set, I actually write a "checklist" of things to do later, either a few hours later, or a few days later, depending on type of release. The main part of it says: Remember to change Equinox promote script name from 'manual-' to 'promote-' when time to promote. Remember to remove 'buildHidden' file, and re-run updateIndexes.sh since HIDE_SITE was true. Remember to add to composite, deferedCompositeAdd.sh, since HIDE_SITE was true Those three steps could easily be made into a "script" to run ... say, called "propmotionStep2.sh" ... = = = = = A corollary improvement ... each promoted build is (eventually) announced to mailing lists ... the note contains specific URLs and DL sites ... at a minimum, the "template" of that note could be produced by the scripts ... if not actually sent by "sendmail". I think I'd start off with a template :)
See also bug 414739 comment 2 for some additional variables that might be useful for long term location of "buildproperties.properties"?
