Address the remaining points after discussion of last week (See minutes of WT Call 06/02/2019)
|1||Backward compatibility||Thorsten, Petr and the team|| |
The presentation proposes the following behaviour identified as 'sliding window':
Example: Version n+1 will be backward compatibility to version n, but probably not to version n-2
This would be a great improvement, because current way of thinking requires operators to
- update all devices and applications to the latest backward compatible version
- before updating the first application or device to a backward incompatible version
- programming effort for continued support of deprecated artifacts
- operational effort for roll-out of releases
There is also proposal to change the way we name the releases (no more 1.x, 2.x etc but with month and year of issue indication like 19.2, 19.10 etc. indicating as well the backward compatibility level with symbol <<.
The topic is quite important but also complex and needs the team to fully understand the scenarios presented (by the real valuable contribution). For this reason, offline discussion is invited, and the topic will be in the agenda of the next WT meeting.
|2||new items for TR-532||A list of the open issues will be distributed to collect the priority input in order to define the order how to address the different topics.|