Write a semantic versioning working agreement document

[taylorkaren]

Task Description

From the 8/1/22 standup conversation: Write a semantic versioning working agreement document that defines what is a "baby" fix, minor fix, major fix, feature, etc. so that we have guidelines for what prefix to use on commits and semantic versioning handles version numbers the way we want it to.

Considerations

• The official documentation for how NPM recommends on how to do this: https://docs.npmjs.com/about-semantic-versioning (thank you, Anish!)
• Is there documentation for the VA overall that we could reference for this?
  • If not, we should put together some guidance for our repo.
• Have a mob session to figure out what we want to do (what types of feature and fixes will we be working on).

Acceptance Criteria

• [x] Semantic versioning guidelines that include the details noted in the Task Description have been documented Confluence document here
• [x] Guidelines documentation has been reviewed by FLT members:
  • [x] Anish
  • [x] BJ
  • [x] Harshil
  • [x] Karen
  • [x] Lauren
  • [x] Micah
  • [x] Nick
• [x] All feedback has been addressed.
• [x] Guidelines documentation is linked to from the following pages:
  • [x] VA Forms System+Core (VAFSC) Work Stream
  • [x] Transition Plan Document

[obliviga]

Here's the official documentation for how NPM recommends on how to do this: https://docs.npmjs.com/about-semantic-versioning

Might help us decide how we want to implement this for VAFSC.

[micahchiang]

Engineering decision document - https://vfs.atlassian.net/wiki/spaces/FLT/pages/2308866093/VAFSC+Releases+will+follow+Semantic+Release+Patterns