Operating System: All
Platform: All

I have no intention of "fixing" [2] - it does not make sense; I cannot go "back in time" - things went into odlparent master in the last few weeks which the infrautils master now depends on. This seems "perfectly normal", to me. Got bigger fish to fry!

We'll just wait until the latest current odlparent is actually available for projects to use, again.

Or we would need a kind of fixed 1.9.0 release of odlparent off master. I thought that was the plan all along - not go backwards in time, but start releasing stable odlparent from master, every week or so.

https://git.opendaylight.org/gerrit/#/c/58369/ which TEMPORARILY addresses this just merged. I personally believe that this is the "wrong" way to go about this (IMHO the idea to "downgrade Nitrogen master projects to 1.8.0-Carbon odlparent was dumb and the wrong way around; IMHO we should have first gotten RELENG-57 ready, release a non SNAPSHOT 1.9.0 odlparent; and taken it from there), but now that as we've already gotten ourselves half way into this mess we're currently in, merging c/58369 with commented out recent work seemed the necessary very short time fix to do anyway.

As per the discussion with Stephen and Robert today recorded on https://lists.opendaylight.org/pipermail/release/2017-June/011197.html, I expect this to get back on track within days and not weeks - the (new) plan discussed today is to have an odlparent 1.9.0 release early next week, and switch all projects (back) to that, and revert c/58369 again.

We'll then have a odlparent 2.0.0 with Karaf 4 only without Karaf 3 in the second half of next week, and go from there.

FTR: jobcoordinator, ready & itestutils actually as of right now isn't building anymore in infrautils, it got commented out in c/58369 .. a patch which re-activates it, now that c/58848 has been merged, is coming up ASAP...

https://git.opendaylight.org/gerrit/#/c/58939/