- Issue created by @smustgrave
- Status changed to Closed: outdated
almost 2 years ago 10:54pm 9 November 2023 - πΊπΈUnited States smustgrave
Changed up how I do things. Only doing a meta for major releases.
- πΊπΈUnited States greggles Denver, Colorado, USA
That seems fine to me. I tend to make a plan issue to help people who want a release work on the most valuable issues.
Somewhat off-topic, I think a new release that includes features should be 2.1.0 according to https://semver.org/
MAJOR version when you make incompatible API changes
MINOR version when you add functionality in a backward compatible manner
PATCH version when you make backward compatible bug fixesAdditional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
So, 2.0.2 would only include backward compatible bugfixes, and 2.1.0 would include backward compatible bugfixes or features or both.
- πΊπΈUnited States smustgrave
Makes sense! Wasn't even planning a 3.0.0 till we can convert to actual plugins.