Pretty much release after each PR, which addresses one issue / new feature.
I just change the version inside my .csproj file and run dotnet build -c Release. My .csproj is configured to build a nuget package automatically, which I'll then publish to NuGet using dotnet nuget push (with my API key etc. added).
I don't worry about old versions of the codebase...what's on master is what everyone should be working from. If not, they should pull/merge the diffs.
With point 1, I would have thought that it may have felt like a lot of releases for small changes. I do see benefits in management of bugs etc (eg. using version 1.2.5 was fine but 1.2.6 is broken - you know exactly where the bug came from) but if you have a lot of changes happening, the versions would have gone up fast. Is this more a case of "stable" development where there isn't a whole lot happening every other day/week?
Ya, in my case, there aren't usually tons of bugs or features to tackle all-at-once. If that were the case then ya, I'd shoot for bundling a few of those into each release.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Pretty much release after each PR, which addresses one issue / new feature.
I just change the version inside my .csproj file and run
dotnet build -c Release. My .csproj is configured to build a nuget package automatically, which I'll then publish to NuGet usingdotnet nuget push(with my API key etc. added).I don't worry about old versions of the codebase...what's on master is what everyone should be working from. If not, they should pull/merge the diffs.
Managing a FLOSS project is tough enough without trying to support old versions. If someone else has a need for the 2.x version, let them maintain it.
Thanks for responding!
With point 1, I would have thought that it may have felt like a lot of releases for small changes. I do see benefits in management of bugs etc (eg. using version 1.2.5 was fine but 1.2.6 is broken - you know exactly where the bug came from) but if you have a lot of changes happening, the versions would have gone up fast. Is this more a case of "stable" development where there isn't a whole lot happening every other day/week?
Ya, in my case, there aren't usually tons of bugs or features to tackle all-at-once. If that were the case then ya, I'd shoot for bundling a few of those into each release.