Test well. Unless a cross-project blocking bug is found, this will become our Juno SR2.
http://download.eclipse.org/releases/maintenance/ But, first a quiet week, to prepare sites, do acceptance testing, update testing, etc. If you find a "bad bug" that only effects your project, you may want to prepare work-around notes or provide a patched feature on your project's software site repository. At this point, stability is more important than fixing every bug, and we are all familiar with the risks of re-spinning (the main one being introducing an even worse bug, and then not having time to adequately test or repair it). I've disabled the aggregation job to help avoid confusion, and will only re-enable it if we find one of those blocking bugs. But do remember to leave your repos and aggregation files "build-able" in case we do need to do a respin. Much thanks,
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
