[TSC-206] BGPCEP Sodium Release plan Created: 15/Mar/19 Updated: 20/Aug/19 |
|
| Status: | Open |
| Project: | tsc |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Project Plan | Priority: | Medium |
| Reporter: | Robert Varga | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| ODL Project: | bgpcep |
| ODL Release: | |
| ODL Participation: | SNAPSHOT_Integrated (Managed) |
| ODL Checkpoint: | Initial |
| ODL New Participation: | RELEASE_Integrated (Managed) |
| Description |
|
We have a Sodium release tracking targeted issues here: https://jira.opendaylight.org/projects/BGPCEP/versions/10908
Overall the focus of this release is going to be stability and addressing technical debt. Contingent on NETCONF transitioning to MRI, we would like to transition to being MRI, too.
|
| Comments |
| Comment by Komer Poodari [ 20/Aug/19 ] |
|
Hi Robert, I am working on Sodium release outbound messaging. I understand from the Sodium release tracking targeted issue list, there is going to be a significant value addition from the BGPCEP project. Could you please elaborate on top-5 additions and their respective benefits to the end-users, system integrators and/or other community projects? As you know, the benefits could include, but not limited to, functionality, scale, performance, reliability, and interoperability. I appreciate your help. Best regards, Komer |