Right now, the cve-schema repo has a main branch which reflects the current deployed version of the CVE Record Format, and a develop branch which reflects the current development version. While this works, it is awkward in the context of GitHub.
I think it may be helpful to transition to main being the development branch, deprecate and remove the develop branch, and use tags and/or GitHub Releases to indicate released versions deployed to CVE Services.
This is me putting a stake in the ground that I'd like to write an RFD for this.
Right now, the cve-schema repo has a
mainbranch which reflects the current deployed version of the CVE Record Format, and adevelopbranch which reflects the current development version. While this works, it is awkward in the context of GitHub.I think it may be helpful to transition to
mainbeing the development branch, deprecate and remove thedevelopbranch, and use tags and/or GitHub Releases to indicate released versions deployed to CVE Services.This is me putting a stake in the ground that I'd like to write an RFD for this.