...
The implementation team will leverage Azure Dev Ops for more detailed tracking of their software development work. The Match-Connect Product Owner will take responsibility for ensuring synchronization of feature inclusion into the detailed work items in Azure Dev Ops.
/* Offer proposals for how we might improve / tighten relationship between Confluence / Azure Dev Ops AND SteerCo and WMDA IT Implementation Team */
Working Group: HPE, Rimke, Mark, Craig, Matt
Feature Impact Categorizations
...
Major changes must be coordinated with the community and should only be made on a periodic basis (e.g. once / year). Minor changes and patches may occur at the discretion of the Match-Connect implementation team, with an aim towards continuous delivery.
Coordination of Major Releases
- WMDA can introduce new versions of the APIs at any time, so long as the existing versions of the APIs still exist
- Then, during a defined period, the community must prepare to receive via the new versions of the APIs
- Once all parties can receive (or at the end of the defined period), any may send using the new versions of the APIs
- Then WMDA may deprecate the old versions of the APIs
Release Notes
Release notes shall be generated coincident with each release of Match-Connect. Depending upon the audience, these notes may be generated from the release candidate page(s) in WMDA Share OR directly from Azure Dev Ops. The implementation team will have a change log (manifest) for each release (major / minor / patch). Release notes may be published for the benefit of end users when there are major changes.
...