Skip to content

5.x - Update version-numbering pattern

Tasks

FAQ

Q: Would it be better to say v4.8.0 vs v5.0.0 vs v5.1803.0 vs v18.3.0 vs v33.0.0?

They're all basically the same. All of these options will give someone the heebeegeebees -- because we've been doing 4.7.x for two years, and anything that looks different will look different, and different is scary.

The fundamental message should be this:

  • The change in number is superficial.
  • The substantive editorial/QA regime for v5.{$Y}.0 is (initially) the same as the previous v4.7.{$Z}.
  • The new numbering makes it to easier to administer minor patch updates, enabling us to consider more fine-tuned maintenance regimes.

There are bikesheddy reasons to favor one or another.

Q: But I think there should be substantive change!

Grand! Please head over to #2 to weigh-in on proposals or add new ones! (Or, if you want to focus-in on the main review criteria, feel free to open a pull-request in civicrm-dev-docs.)

Q: Does this mean you're going to start making more, bigger, scarier changes more often?

No. This is strictly a superficial realignment of the numbers. In fact, the general tenor of editorial policy has been toward tightening rather than loosening standards.

Edited by totten
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information