Hi David, it's my first release for Papyrus and I have problems with my current documentation. I think to finish tomorrow in the morning with my colleagues. (here it is 9:45PM). In this case, I think Papyrus build process will be finished thursday at 4AM Eastern. Could you wait us?
Cheers, -- Vincent Lorenzo ________________________________________ De : cross-project-issues-dev-boun...@eclipse.org [cross-project-issues-dev-boun...@eclipse.org] de la part de David M Williams [david_willi...@us.ibm.com] Date d'envoi : mercredi 18 janvier 2012 20:58 À : cross-project-issues-dev@eclipse.org Objet : [cross-project-issues-dev] Status and outlook for Indigo SR2 RC1 warm-up build tick tock Here we are already at 3 PM on +3 day. Unless someone shouts "wait", I'll consider the updates for RC1 finished by 5 PM today (Eastern), and what ever build is current will then become our "maintenance" staging repo for RC1. http://download.eclipse.org/releases/maintenance/ There are two contribution files that have disabled features or repositories ... riena being the largest omission ... last call! :) ep.b3aggrcon (see bug 362103) riena.b3aggrcon Markus tells me, in keeping with tradition, he will produce the EPP packages with the same spirit of "warm-up" (not moved to downloads, not mirrored, no official sign-off, but the maintainers (or, anyone) can still test from the EPP build site. In two short weeks we'll produce RC2 which overlaps with Juno M5! ... so, plan accordingly ... I'm sure we'll be keeping the build machine(s) warm that week. Indigo: http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan#SR2 Juno: http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Schedule Thanks, _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev