Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Clarify YY.MM update rule

...

  • YY: Year (20, 21, 22, etc.)
  • MM: Month (1, 2, 3, ..., 11, 12). 
  • Patch: Fortnightly releases, or whenever non-quarterly releases happen Ideally, no breaking changes, like our current policy is.
  • YY.MM.patch: The year and month of are from the current  current “quarterly” release. NOT the Not the current month. For . The YY.MM value is taken set during the first release candidate. For example, if we release 20.10.0-RC1 in late October, then the next patch release will be and the proper release goes out in November, it will still be 20.10.0. Then, the patch value is the only one that will be incremented until the next quarterly release. For example, the next release will increment to 20.10.1, even if it is in November. Patch: Fortnightly releases, or whenever non-quarterly releases happen Ideally, no breaking changes, like our current policy is.20.10.2, 20.10.3, etc. even as patches are released in November, December and January 20201. 

The YY.MM.0 release indicates a release that underwent harsher than normal QA processes and testing, and is also a release where users should be sure to check for breaking changes.

...