Hi David, could you please update the corresponding google calendar? I've imported the linked iCal file, but can't find any Luna milestones entries.
Best regards, Dennis. Am 12.08.2013 um 14:20 schrieb David M Williams: > You just have to check from time to time. There's no automatic enablement. > > > > > From: Igor Fedorenko <ifedore...@sonatype.com> > To: cross-project-issues-dev@eclipse.org, > Date: 08/12/2013 07:06 AM > Subject: Re: [cross-project-issues-dev] Ready for Luna (M1) > aggregation > Sent by: cross-project-issues-dev-boun...@eclipse.org > > > > I am not sure I understand the expected process for projects that have > their dependencies disabled in the aggregator. Are we supposed to check > from time to time to see when dependencies become enabled or there is a > way to tell b3 aggregator "enable contribution when all prereqs are > available"? > > -- > Regards, > Igor > > On 2013-08-09 6:06 PM, David M Williams wrote: > > I hope everyone has enjoyed their summer vacations ... but now back to > > work! :) > > > > We do have a preliminary schedule for Luna milestones, see > > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule > > (though, that one table is only part of that document to review, at the > > moment). > > > > The complete schedule is still open for review and "tweaking", but the > > first several milestones are pretty much a given, and the first one is > > due in two weeks! The overall schedule (of having approximately 6 week > > milestones) is pretty much just like previous years. The one main > > difference is that we "moved up" M5 and M6 to make sure M6 finished > > before EclipseCon 2014 started (so ... we don't allow an "extra week" > > for end-of-year holidays) and this M5 and M6 change means M7 is a week > > longer than usual: 8 weeks instead of 7! > > > > As always, we hope everyone in 'kepler' stays in 'luna', but ... to make > > sure ... we require explicit "buy in". In practice, this means I started > > the 'master' branch with what ever it was for Kepler, but then set > > enabled="false" for everyone's contribution. If you plan to be in Luna, > > please removed the enabled="false" from your "contribution element". If > > you are not quite ready to actually make a contribution, you can put > > enabled="false" in your "repository element" to signify the difference > > of "planning to participate", but "contribution not ready yet". If > > nothing else, you may simply have to wait until your pre-reqs make their > > contributions. > > > > I have enabled the contributions for Eclipse and Equinox (with out > > likely Luna M1 content), and produced a preliminary "staging" repo ... > > which has only those two projects in it, at the moment. > > > > Let the fun begin! As always, questions to this list are welcome. > > > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev Dennis Hübner Xtext Commiter / Build Engineer Mobile: +49 (0) 151 / 17 39 67 07 Telefon: +49 (0) 431 / 990 268 70 Fax: +49 (0) 431 / 990 268 72 itemis AG Niederlassung Kiel Am Germaniahafen 1 24143 Kiel http://www.itemis.de/ Rechtlicher Hinweis: Amtsgericht Dortmund, HRB 20621 Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter, Sebastian Neus Aufsichtsrat: Dr. Burkhard Igel (Vors.), Stephan Grollmann, Michael Neuhaus
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev