On 06/04/2013 11:33 PM, Max Rydahl
Andersen wrote:
Await approvals from build, affected team leads and
project lead(s). In case of urgency build + one project lead is
considered ok, but should be the exception.
Updates of Eclipse version are specifically affecting no-one, and I
fear it's not about to get much feedback. It's a low-risk change and
the later we apply it, the later we'll know whether everything works
fine with newer TP.
A too long feedback loop (several days) is not very possible in the
RC stream with a new release of Eclipse release train every week.
To give feedback the changes looks good on first roll but change
from planner to slicing (which I normally would consider good)
should be confirmed first. i.e. what dependencies will *not* be
included now ?
These could easily escape being detected in builds thus would be
great to outline them in such a change.
Have you compared the list of bundles in generated TP with and
without this slicing/planner mode ?
It won't affect builds.
The mirror-target-to-repo mojo is actually a "slicer", so the output
site for target-platform does not depend on planner/slicer, it's
always the same output as slicer. So moving TP from planner to
slicer in multiple makes it easier/faster to detect mistakes that
used to occur only while validation unified target. Those issues are
now detected while validating multiple (about 1 hour earlier).