You just have to check from time to time.
There's no automatic enablement.
Igor Fedorenko <ifedorenko@xxxxxxxxxxxx>
08/12/2013 07:06 AM
Ready for Luna (M1) aggregation
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
On 2013-08-09 6:06 PM, David M Williams wrote:
> I hope everyone has enjoyed their summer vacations ... but now back
> work! :)
> We do have a preliminary schedule for Luna milestones, see
> (though, that one table is only part of that document to review, at
> The complete schedule is still open for review and "tweaking",
> first several milestones are pretty much a given, and the first one
> due in two weeks! The overall schedule (of having approximately 6
> milestones) is pretty much just like previous years. The one main
> difference is that we "moved up" M5 and M6 to make sure
> before EclipseCon 2014 started (so ... we don't allow an "extra
> for end-of-year holidays) and this M5 and M6 change means M7 is a
> longer than usual: 8 weeks instead of 7!
> As always, we hope everyone in 'kepler' stays in 'luna', but ... to
> 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
> 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
> I have enabled the contributions for Eclipse and Equinox (with out
> likely Luna M1 content), and produced a preliminary "staging"
> 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 mailing list