I just wanted to raise that we have also discussed removing opendaylight-karaf-empty altogether, which is tied to transitioning the remaining projects over to inherit from features-parent IIRC (including the main line integration/distribution which currently uses opendaylight-karaf-empty). It has been a long time since I have had time to look at this issue, so I could be a little bit off with my description here...
>From a Brocade standpoint, we came to grips with the fact that it is large for now and can be improved in the future, but haven't prioritized that work. I also know multiple vendors (us included) inherit from opendaylight-karaf-empty to produce our downstream distributions, so please keep me in the loop with what is decided going forward! Regards, Ryan Goulding On Mon, Dec 5, 2016 at 11:23 AM, Robert Varga <n...@hq.sk> wrote: > On 12/05/2016 05:17 PM, Michael Vorburger wrote: > > Does opendaylight-karaf-empty's version *HAVE* to identical to the > > odlparent version? Why? How about odlparent/karaf has a separate > > versioning than the rest of odlparent? > > Having separate versioning is fine, having a separate release cycle is > not -- at that point it becomes a separate project and should be treated > as such. > > Regards, > Robert > >
_______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
