Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Implement semantic versioning and a matching CI build #13

Closed
11 of 12 tasks
Martin-Bohring opened this issue Jul 1, 2016 · 0 comments
Closed
11 of 12 tasks

Implement semantic versioning and a matching CI build #13

Martin-Bohring opened this issue Jul 1, 2016 · 0 comments

Comments

@Martin-Bohring
Copy link
Owner

Martin-Bohring commented Jul 1, 2016 •
edited
Loading

This is to capture my current thinking on versioning, CI and artifact publishing.

  • Semantic versioning 2.0
  • Version updates are driven by the RELEASE_NOTES file (versioning is a human activity after all)
  • Version updates happen only on the master branch
  • Version Updates create a new version tag on the master branch
  • AppVeyor build numbers are not used (I am torn in 2 directions here, but see item 1)
  • AppVeyor builds on all branches
  • Unit test and specification execution on all branches
  • Release builds on the master branch
  • Debug builds on all other branches
  • Artifact creation only on the master branch with a version tag
  • GitHub releases are only created on the master branch with version tag
  • Nuget publication only happens on the master branch with version tag (Still not sure if I should trust AppVeyor with Nuget keys. Update: I decided to trust them)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Martin-Bohring