EPP: feature="org.eclipse.emf.cdo.sdk" is included in the
modeling package, therefore it should be included in this package if it
builds.
But speaking of the modeling package: In yesterdays build there were
unresolved dependencies.
It's strange: Using the staging site I'm seeing CDO in the Modeling
category. Net4j is missing. If I install CDO the Net4j plugins are
implicitely installed, too. And according to the EPP site both are
missing.
Just a reminder that M5 is
coming
up.
2/5 is the very last day of the M5 window ... we all need to meet our
contributions
before then! ... and the +0 date is this Friday (1/29). So, not a lot
of
room for error or delays.
Please keep an eye on your
helios
contributions,
to make sure they can be aggregated correctly, without error. The
expectation
is that "breaks" will be corrected within a few hours. If they
can not be, keep us all posted about outlook here on this list.
If this isn't done, I'd likely
have
to pull the breaking component out, plus all its dependents, and that's
a whole lot of extra work (for me) and adds a lot of risk and
uncertainty
to the milestone (for everyone else). As always, we will declare on
time!
I also wanted to remind you that
the
deadline for CQ's is the end of M5 (2/5). This is an important deadline
since it allows "budgeting" for the required IP work. CQs submitted
after that date may not be (or I should say will likely not be?)
approved
in time for Helios and could thus prevent you from releasing as you
plan.
So get those CQs submitted! And/or ask questions (now!) if you have
some
special case.
Lastly, tracking. We are making
some
progress on getting an on-line system to track compliance to
requirements,
but it will not be done by M5 as I once fantasized. Thus, I'll prepare
a shortened "check list style" version of the requirements
document, http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php
as some of you have requested.
Details
later.
