Ramon Casellas the process should apply only to Long Term Support (LTS) releases.
Karthik Sethuraman a good criteria for a release to be an LTS one is when it can fully replace a former LTS release.
Ramon Casellaswe need to synchronize the RIA and TAPI releases.
Karthik Sethuraman the overall process shall start from requirements and use cases, which shall be agreed before to update the model accordingly. Top down approach.
Karthik Sethuraman Explore usage of Jira - User Stories. In MEF we agreed to move from traditional word/pdf documents to the Agile approach.
Ramon Casellas we have a limited workforce to adopt a further mechanism. Karthik Sethuraman Jira/Agile can be adopted also by small projects.
User Stories can be composed by more Use Cases.
Nigel Davis there is a volume of work and the workforce is scarce. We reviewed the RIA 1.1 starting September 3 till last week, 10 weeks with 2/3 calls per week, 2 hours per call.
Arturo, it took about 3 years to consolidate the RIA 1.0 and its TAPI version 2.1.3. We can expect another couple of years for the next big version.
Arturo, the TIP MUST will deliver, likely in a couple of weeks, the Requirement specification, which will be the input for next works in TAPI.
Andrea Mazzini Currently the RIA is focused on implementation agreement rather than on requirements and use cases.
Ramon Casellas For instance, more insights are necessary on several attributes and values.
Nigel Davis , Ramon Casellas concept of background use cases, maybe in a specific appendix, to explain the usage of parameters.
Summary of agreements:
From now on, organize the TAPI agenda more on requirements and use cases rather than direct model proposals.
Synchronize RIA and TAPI deliveries.
Plan a TAPI/RIA LTS delivery per year. Minor releases only for bug fixing detected on LTS deliveries.
Progressively add to the RIA the requirement and use case aspects.
Early December start building RIA 1.2 for TAPI 2.3.x - major feature OAM for digital OTN. Plan 2 calls per week, 3 hours per call, till March 2022.
Side discussion on TAPI OAS, Ramon Casellas points out that it is not Restconf compliant due to lack of name space usage.
Arturo agrees that TAPI OAS, despite some minor deviations from Restconf, is still valuable. E.g. can be input of Postman for the model validation.
For further consideration how to improve the current translation.