Package versioning

[ThomUK]

Today v0.1.0 of this package is on CRAN, and the github main branch has moved beyond that version to v0.1.0:9000. However, using this development version in production would be risky because of the possibility of accidental breaking changes.

What is the best versioning strategy for the minor fixes and feature additions that are being included periodically, before v0.2.0 goes to CRAN?

Could i propose that we start to use the 3rd digit of the version number for minor bugfix changes eg. v0.1.1

This might allow production users to take advantage of the latest changes without risking accidental breaking changes in production work.

[ChrisBeeley]

We do semantic versioning in our team, which I think is what you're referring to (?) and yes I agree it's a good way to go. I mean, I don't write any code in this repo, so what do I know, but that's my opinion anyway 😝

[ThomUK]

Semantic versioning is what i was trying to remember, thanks!

[tomjemmett]

Worth having a quick catchup, I think we are probably at a point to call this 0.1.1 and get pushed to CRAN

[Lextuga007]

Could we make a catch up open to all? I don't think you'll be inundated with people and this is a great question for package developers. I'd definitely like to come!

[ThomUK]

Definitely, how is Weds morning next week?

[tomjemmett]

I'm free anytime 8.30 - 11 :-)

[ThomUK]

There's a loose plan to meet on this next Weds - please dm me on slack to join or propose a better time...