Skip to content

Milestones

List view

  • User stories and issues to support the ADP role

    No due date
    9/9 issues closed
  • No due date
    0/2 issues closed
  • Milestone containing community suggested changes to CVE Record submission and update functions.

    Due by November 19, 2021
    142/143 issues closed
  • No due date
    6/11 issues closed
  • An eternal milestone to keep record of issues documenting technical debt.

    No due date
    0/1 issues closed
  • Stories for deployment of v1.1.0 release

    No due date
    6/6 issues closed
  • This milestone holds the absolute minimum features needed to release an internal Record service.

    Due by March 31, 2021
    7/7 issues closed
  • This Epic holds the work and experimentation necessary for the development team to explore how to meet the requirements of Record Service 1A. Challenges arise due to CVE Schema 4.0 having three separate schemas or structures for a CVE Record depending on the state of the record. We'll need to investigate how different these three formats are and if they're compatible with each other (overlap). This raises questions like how to cleanly implement an interface that allows CPS to submit a CVE record that could be structured in three different ways without complicating the service on the back end. It also means CPS must submit and communicate through the Record service endpoints to change state, as the structure of the Record itself changes when state is changed. The goal of this epic would be to simply investigate the CVE Record 4.0 JSON Schema and build enough `/cve` endpoints where a CVE with an existing CVE ID can be at the very least published but hopefully also capable of going through all possible states of a CVE.

    Due by March 17, 2021
    1/1 issues closed
  • Milestone to serve as a backlog of phase 1A delivery of the Record service

    No due date
    9/9 issues closed
  • User Stories that enable default users to see and do additional functions in the User Registry

    Due by February 17, 2021
    5/5 issues closed
  • This epic represents user stories that expand the secretariats abilities to get the users and orgs that exist in the system.

    No due date
    1/1 issues closed
  • This epic contains user stories that add the role of org admin to the system and provides permissions for the org admin that allows the role to conduct some general account administration tasks.

    Due by March 3, 2021
    5/5 issues closed
  • This milestone serves as a collection for user stories that define requirements for the Record Service.

    No due date
    1/11 issues closed
  • This milestone contain tasks aimed with the goal of paying some technical debt generated by focusing on IDR deployment. It is time-boxed to the beginning of the holidays, but could be considered done sooner. Major points include: Implementing the repository pattern in the codebase; moving errors out of constants and into local error packages that utilize functions to form the errors in a consistent format; removing the use of a if (!returned) code style in the controllers; and vetting logging statements in the code for relevance and ensuring all statements print in a consistent JSON format for ease of parsing.

    Due by December 30, 2020
    9/9 issues closed
  • This milestone holds issues that contribute to the goal of having certain developer workflows operate within GitHub Actions. Once the following actions exist, this milestone can be considered finished: an action triggers upon updates to a developer's feature branch that executes the automated tests in order to notify the developer early if changes have broken code; a community pipeline exists that acts as a mirror of the latest services release so the community can exercise code against this endpoint when developing their tools to integrate with the services, and another community pipeline exists to serve as a feature pre-release for community evaluation and testing of new code before delivery.

    No due date
    1/1 issues closed
  • A milestone to hold issues that pertain to supporting or expanding the open source service project.

    No due date
    1/3 issues closed
  • No due date
    2/8 issues closed
  • No due date
    18/18 issues closed
  • Due by June 22, 2020
    1/1 issues closed
  • Due by May 25, 2020
    4/4 issues closed
  • Due by April 30, 2020
    1/1 issues closed
  • First official sprint for AWG

    Due by April 27, 2020
    1/1 issues closed
  • No due date
    4/4 issues closed