Skip to content

Release Cycle Report 3 23 2021 v1.1.0

Jump to bottom
Matt Bianchi edited this page May 10, 2021 · 2 revisions

Community Features for Release

Expanding the abilities of default Users in the system

https://github.com/CVEProject/cve-services/milestone/21?closed=1

General Users can now:

  • edit their own information
  • refresh their API token
  • see their Organization's information
  • see other Users that belong to their organization

Enabling the role of Org Admin for User Registry

https://github.com/CVEProject/cve-services/milestone/19?closed=1

A new Org Admin role has been added to the User Registry.

An Org Admin can now perform these actions for Users within the same organization as the Org Admin:

  • update another User's information
  • reset another User's API token
  • activate/deactivate another User
  • register a new User

"Internal Features" for Release

Record Service Phase 1A MVP

https://github.com/CVEProject/cve-services/milestone/24?closed=1

The decision has been made to take the first step of releasing a Record service by first deploying it internally. This allows the development team to continue a stepped approach of modifying the legacy system to give up major program responsibilities.

With this initial deployment, the Record service will take new records, allow updates, and list records with the ability to filter on modified dates. All of these endpoints will be restricted to Secretariat accounts.

Deployment

As we enter our first Release cycle, the deployment process has been broken up by two, two week sprints:

March 17-31
Dev Team

  • Finish feature development (listing CVE Records)
  • Create a release branch off dev effectively establishing a code freeze
  • Comb over project for maintenance
    • Update Developer Guide on the GitHub Wiki
    • Review OpenAPI documentation

Operations

  • Develop data migration script for past records from CPS -> Record service
    • Test migration in integration
  • Create a Deployment Manifest for release
    • (a stepped check document for deployment)

April 1-15
Dev Team

  • Staying available for needed hot fixes to release branch

Operations

  • Practice Deployment Manifest in integration and refine
    • Data migration
    • Regression tests
    • Integration tests
  • Based on results, establish official deployment date
  • Deploy
    • Announce planned deployment date on list
    • Announce successful deployment on list
Clone this wiki locally