Closed julienmoumne closed 7 years ago
tsteur
commented
8 years ago Determining the next version:
I'd suggest to follow http://semver.org/ which also helps on deciding to determine the next version
Current version of piwik-dotnet-tracker 2.16.0 does not correspond to either versions of Piwik and piwik-php-tracker.
I would mention in the README that the version is not related to the Piwik version
In general: The version scheme for this should be independent from any other tracker and Piwik
julienmoumne
commented
8 years ago Thanks for the feedback.
Do you also imply it is acceptable to start from v2.16.0 instead of finding a way to somehow reset at v1.0.0?
tsteur
commented
8 years ago I would probably start from 2.16.0 as it would be otherwise confusing when having already released a 2.X version for this tracker.
mattab
commented
8 years ago Sounds good to use 2.16.0
The new C# SDK was advertised in the 2.16.2 blog post: https://piwik.org/changelog/piwik-2-16-2/ and on social network eg. https://twitter.com/piwik/status/762498653327990787
julienmoumne
commented
7 years ago julienmoumne
commented
7 years ago New version will be 3.0.0 since the public API changed.
Before June 2014, piwik-php-tracker was part of Piwik's code base and therefore followed Piwik's versioning scheme. When it became a separate project, version number went from v2.x.x to v1.0.0.
piwik-dotnet-tracker was a separate project from the beginning but followed the versioning scheme of Piwik and its tracker. This made bookkeeping convenient when porting the code base from PHP to .NET.
Current version of piwik-dotnet-tracker 2.16.0 does not correspond to either versions of Piwik and piwik-php-tracker.
piwik-dotnet-tracker should have its own version scheme since:
piwik-dotnet-tracker would benefit from semantic versioning and autogenerated changelogs with, for example, skywinder/github-changelog-generator.
Main issues to address: