SemVer or continue with 0.1.++ ?? about teams-for-linux HOT 7 CLOSED

I'm a big fan of frequent releases and semver. Makes everything far simpler.

That would be my vote.

from teams-for-linux.

Ok, talking about numbers (and not the how). I think that this a temporary project, until MS supports Linux.
We don't know when is going to be that. And besides that 0.1.x versions was OK to begin as the missing features and errors were multiple, but right now that's not the case, so, I think that we should start making Semantic versioning and define 1.0 version when CI/CD is on place on all the current platforms. And if there is a similar brake on "API" (e.g. change on User Agent) that requires deletion of profile then we should increase the first digit.

About the how, https://github.com/semantic-release/semantic-release/blob/master/README.md seems great but I don't know if it's worthy to complicate all with more dependencies and stuff. I like the idea but it will take time and I don't see a big problem to be solve.

from teams-for-linux.

Seems like you two are on board with the semver.

Ok, I also think that probably is also best to pack stuff in releases. This is mainly to avoid making package maintainers job easier (like arch and snap). I don't think people want to be doing builds every few day... it is maybe ok every week, but you don't want people hate us.

Should we move then to 0.2.0 (as there are new features) for this release (instead of 0.1.18)?

I am happy to then increase the release number depending on what is been release (patch = bugs, minor = features, major = breaking changes).

Probably we can revert back to tell people can create PRs to Master and we/I can deal with determining the version number.

I agree semantic-release might be a pain.. but I might give it a try as it could, in theory, creates the release notes and all that part for me/us. So I can concentrate on doing more important stuff.

from teams-for-linux.

Minor note on the snap - I do expect that to be nearly hands off, as that would be part of CI. Master branch hits the edge channel, and releases automatically get pushed to the main channel.

from teams-for-linux.

Maybe we can investigate this as an option:

https://github.com/semantic-release/semantic-release/blob/master/README.md

Automation all the way.

from teams-for-linux.

I will see if I can get that working at some point. At the moment, lets continue just packing up in master and, when a release is ready, increase the version one point.

If/when more people starts to contribute, we can revisit the idea.,,,

from teams-for-linux.

Ok, I just updated the main README.md to indicate we are using SemVer but people should not worry to increase the number... I/We can decide before a release what number release it with.

The only thing is that, after a release, I will increase the lower version number. Like now that is 0.1.18. That way, we don't re-release previous releases.

Once we are ready to release, we can either leave the number (if only bug fixes) or increase the minor or mayor depending on the case.

Closing this :) Thanks for the input!

from teams-for-linux.