Ah, yes, it's this one: https://docs.opendaylight.org/en/latest/release-notes/upgrade-process.html#binding-dtos-enforce-non-null-keys Thanks for noticing, yeah, the document needs polishing

Hi Robert, Do you know if the lispflowmapping failures are related to one of the items on the MD-SAL impacts list on this document?

So we have real progress (thanks, Richard) and are down to two projects: lispflowmapping and netvirt, both of which need attention from regular committers. Lispflowmapping is the easier, as it has

Hello everyone, this is yet another wall of text from me. TL;DR is: we want to give visibility of easy tasks so that even causal ODL users see where they can contribute. If that interests you,

Hello TSC and all We are going to code freeze Aluminum for all Managed Projects ( cut and lock release branches ) on Monday October 26th at 10 am pst. Please remember that we only allow blocker bug

As discussed on today's TSC call, I have created the following archive proposals. Can we get a vote for archiving the projects as per the TSC

Hello everyone, this is a heads up that the "Version Bump" step of Silicon release is happening right now. The patches to managed projects are staged

I have created a draft proposal for TSC Election Process here: https://wiki.opendaylight.org/x/0BQF We can discuss this at tonight's TSC meeting. Best, Casey Cain Technical Program Manager /

here's another one that focuses specifically on the usecases for the upgrade flag, (some things are slightly dated implementation wise, but the general idea is all

hi robert, not sure of documentation, sorry about that. we did present this in a ddf, the slides are here - Upgrade @ DDF 2018 Upgrade @ DDF 2018 Netvirt Upgrade, Oxygen and Beyond Daya Kamath,

Thanks for letting us know.

-- Tejas. S. Nevrekar Mobile: +91-99805 31339 Bangalore, INDIA.

Hi Robert, Unfortunately, I couldn't find any User Guide as such for this Upgade-Flag(@Faseela K, Please point us if there any) This UpgradeState Flag utility was earlier implemented in GENIUS

We as long as the soon to be self managed projects such as netvirt can work on Aluminium SR1 csit, we can probably release it on time.

I think this could be done just before a release milestone (e.g. for a RC) but difficult to achieve in a continuous way like in AR today, specially when projects will have freedom for updating their

Right, but we already have this defined -- and it is the SimRel participation rules for all MRI projects -- irrespective of any other label that may be perceived as relating to a particular project

I also do not think TSC can obligate a project to release but I think we have to set some rules for functioning together, for example Platform projects should define a set of release versions for

Yeah, except the TSC does not have the mandate for most of these things. Remember, the TSC gets a say only in two cases: - project lifecycle events (creation, graduation, etc.) - project SimRel

Hi all, I personally found very interesting the ODL release model conversation we held in DDF. In particular I would like to see if the current project classification and release model: MRI, MSI, SM

This work has now been completed -Andy- -- Andrew J Grimberg Manager Release Engineering The Linux Foundation