Process or notifications to avoid breaking customer applications with platform upgrades but staying RFC compliant at the same time Jeff Hartley will be joining for this
Jeff Hartley talks about the impact of API changes on downstream consumers (commercial & other open source projects like ONAP).
Some highlights, including actionable items:
General guidance is already to align breaking changes to major releases rather than SRs; these is general agreement that this is the most-desired practice. (This applies to both Behavior and API changes.)
General agreement that maintaining backward- and/or forward- compatibility for necessary breaking changes is too much work for existing teams w/o substantial add'l contribution.
TSC needs ACTIONABLE complaints when things are breaking changes, not just general complaints. i.e. name specifci JIRA tickets that users have issues with (or think may cause an issue going forward). Those of us representing downstream customers/orgs can help make these complaints more useful.
Long-tail consumption of old releases, and length of time between release and consumption, sometimes mean that end-users are not heavily exercising features in their use-cases/businesses until long after the feature is released. Jeff Hartley and others started more aggressively pushing some downstream communities like ONAP to 'catch up" closer to current ODL releases; more of this worldwide "catch-up" advocacy would help (keep things closer to -current).
Need more test cases contributed that reflect ACTUAL user/network/device/service behaviors in use. These can be contributed by anyone that's a user, customer, contributor, or advocate.
ODL-discuss mailing list participation dwindling (another case of "number of users exceeding number of contributors). One method of increasing contribution to Q&A might be more cross-linking into the Wikis of other projects and downstream consumers, as well as those w/formal product support encouraging their support teams to contribute answers, solutions, and comments during slow times.
Releases
Aluminum. AR is having issues with BGPCEP and INFRAUTILS. Robert Vargais helping with fixing some INFRA issues and Jamo Luhrsenhelping with BGP. MRI Bumps checkpoint are due on so we have little to fix these issues. We will follow via email on these issues.
Magnesium SR1 code freeze will be announced on to all projects. Freeze will happen in so we can release Magnesium SR1 on
Release checklist template is updated at Release Checklist Template so please provide us any feedback. We will using it for Magnesium SR1