[orbit-dev] S20170120205402 is gone and Platform-Neon-Maint can not be b

[Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>]

Hi,

Starting with this weekend our internal Platform-Neon-3+ builds are
failing because there S20170120205402 is referenced, I guess it should
reference "R20170307180635".

I don't think Orbit is to blame here because how can it be that
Platform-Release-Builds depend on NONE-Release builds from other
projects, i noticed this in other parts of the platform build as well
(eg referenceing CBI-SNAPSHOTS), so it looks like a common theme.

I don't think this is how a stable build story should be configured and
run. If things fall apart within 1+ year how an this build story be used
for something like LTS?

Tom

-- 
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck