Of course, if someone else depends on your code, and must compile on top
of it ... then that's between you and the dependent project. And, I just
say that for the sake of everyone. These dates I talk about are the latest
possible dates to get in common discovery sites, and EPP builds. Not
necessarily what pair-by-pair projects need.
I'm not aware of any projects depending on CDO or Net4j. If some do
nevertheless, please drop me a note.
Thanks,
From:
Eike Stepper <stepper@xxxxxxxxxx>
To:
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date:
09/11/2009 10:36 AM
Subject:
Re: [cross-project-issues-dev] Remaining SR1 Daze
Sent by:
cross-project-issues-dev-bounces@xxxxxxxxxxx
Hi David,
As I mentioned in my last post to this list, I'm really struggling with
my builds for several reasons since I moved to Athena/Hudson. I couldn't
spend too much time on these issues since I'm currently on vacation (in
Toronto!). Just in case I manage to have good maintenance builds during
next Monday and can promote them to the EMF update site, would that be
too late to get something into Galileo SR1?
Cheers
/Eike
----
http://thegordian.blogspot.com
David M Williams schrieb:
Unless others have suggestions or fine-tuning to make, here's how I
propose we handle the remaining time to SR1 Release, as outlined in
http://wiki.eclipse.org/Galileo_Simultaneous_Release#SR1
9/18 (Friday): End of Final Builds. All code done, but do not promote or
announce anything yet.
Take a few days of final sanity checking, deep breaths, preparation of
webpages, etc.
9/24 (Thursday): Promote Day. At 9:00 AM Eastern start putting content
on
final download site (but do not make "visible" yet). Similar for your
final update repositories. We'll presume everyone is finished by 3:00 PM
Eastern (let us know if you can not make these times). Mirrors will be
populating overnight.
9/25 (Friday): Release. Starting at 9:00 AM Eastern, content can be made
'visible' and announcements made on mailing lists, new items, etc.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev