Any thoughts about version numbering for plugins?

Kirby 2 Solved ✅
1

How do handle version numbering for your plugins or what do think is a good way?

I’m asking because I made a really small fix for Kirby Focus and know I’m not sure if this will be version 1.1 or 1.0.1? Or even a kind of “silent update” keeping 1.0?

I know this is a really special problem and maybe not that important, but I would like to know what you think. Thanks :wink:

2

A generally accepted rule is
Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

*taken from semver: http://semver.org/

2 Likes
3

Npm is also using the semver approach and suggests the following:

  • Bug fixes and other minor changes: Patch release, increment the last number, e.g. 1.0.1
  • New features which don’t break existing features: Minor release, increment the middle number, e.g. 1.1.0
  • Changes which break backwards compatibility: Major release, increment the first number, e.g. 2.0.0

See: https://docs.npmjs.com/getting-started/semantic-versioning

1 Like
4

Thanks for your replies!