When should a commit not be version tagged?2019 Community Moderator ElectionShould a github maintainer...
If a druid in Wild Shape swallows a creature whole, then turns back to her normal form, what happens?
Why zero tolerance on nudity in space?
What prevents the construction of a CPU with all necessary memory represented in registers?
What can I substitute for soda pop in a sweet pork recipe?
How to mitigate "bandwagon attacking" from players?
How can I handle a player who pre-plans arguments about my rulings on RAW?
What is the difference between throw e and throw new Exception(e)?
How to deny access to SQL Server to certain login over SSMS, but allow over .Net SqlClient Data Provider
Creature spells vs. ability to convert a permanent into a creature
How to approximate rolls for potions of healing using only d6's?
How to properly claim credit for peer review?
Should I choose Itemized or Standard deduction?
What is better: yes / no radio, or simple checkbox?
How to visualize a Cayley graph in this style?
Is there any relevance to Thor getting his hair cut other than comedic value?
Is there a German word for “analytics”?
CBP Reminds Travelers to Allow 72 Hours for ESTA. Why?
How do ISS astronauts "get their stripes"?
How would we write a misogynistic character without offending people?
Reason Why Dimensional Travelling Would be Restricted
Hacker Rank: Array left rotation
Whom do I have to contact for a ticket refund in case of denied boarding (in the EU)?
g++ and clang++ different behaviour with recursive initialization of a static member
What do the pedals on grand pianos do?
When should a commit not be version tagged?
2019 Community Moderator ElectionShould a github maintainer rewrite author's in pull requests?Looking for good practices on managing branches and developers in GitHow to use github, branches and automatic releases for version management?Squashing commits from multiple developers into a single commitHow to version when using trunk based developmentpackage and version strategies in a multi repository environmentWhat version numbers should I assign to builds on different branches as part of continuous integration for NET Core-based projects?How to convert the last rc (or other pre-release) into the production version using semver?What is structure of versioning process?Git branch management vs deployable environments
Context: I recently found out about Semantic Versioning, and am trying to determine how to best use it practically for my own projects.
Given that semver takes major changes, minor changes, and patches into account for versioning, when should a commit not be tagged with an updated version? It seems to me that every change would fit into one of these categories, and so every change should be versioned, but when I look at various popular projects on GitHub this doesn't seem to be the way things are done (just looking at the fact that large projects have tens of thousands of commits, with only hundreds of tags).
programming-practices git semantic-versioning tagging
add a comment |
Context: I recently found out about Semantic Versioning, and am trying to determine how to best use it practically for my own projects.
Given that semver takes major changes, minor changes, and patches into account for versioning, when should a commit not be tagged with an updated version? It seems to me that every change would fit into one of these categories, and so every change should be versioned, but when I look at various popular projects on GitHub this doesn't seem to be the way things are done (just looking at the fact that large projects have tens of thousands of commits, with only hundreds of tags).
programming-practices git semantic-versioning tagging
@NickAlexeev Sure, done.
– VortixDev
1 hour ago
3
Is every commit to master a stable, tested, quality assured release in your project?
– Alex Reinking
1 hour ago
@AlexReinking Every commit is tested, but I'm just trying to get accustomed to common practices with my personal projects, so it's just me working it and as such there isn't really a system in place other than "make a change, test it myself, commit it".
– VortixDev
1 hour ago
add a comment |
Context: I recently found out about Semantic Versioning, and am trying to determine how to best use it practically for my own projects.
Given that semver takes major changes, minor changes, and patches into account for versioning, when should a commit not be tagged with an updated version? It seems to me that every change would fit into one of these categories, and so every change should be versioned, but when I look at various popular projects on GitHub this doesn't seem to be the way things are done (just looking at the fact that large projects have tens of thousands of commits, with only hundreds of tags).
programming-practices git semantic-versioning tagging
Context: I recently found out about Semantic Versioning, and am trying to determine how to best use it practically for my own projects.
Given that semver takes major changes, minor changes, and patches into account for versioning, when should a commit not be tagged with an updated version? It seems to me that every change would fit into one of these categories, and so every change should be versioned, but when I look at various popular projects on GitHub this doesn't seem to be the way things are done (just looking at the fact that large projects have tens of thousands of commits, with only hundreds of tags).
programming-practices git semantic-versioning tagging
programming-practices git semantic-versioning tagging
edited 1 hour ago
VortixDev
asked 1 hour ago
VortixDevVortixDev
1245
1245
@NickAlexeev Sure, done.
– VortixDev
1 hour ago
3
Is every commit to master a stable, tested, quality assured release in your project?
– Alex Reinking
1 hour ago
@AlexReinking Every commit is tested, but I'm just trying to get accustomed to common practices with my personal projects, so it's just me working it and as such there isn't really a system in place other than "make a change, test it myself, commit it".
– VortixDev
1 hour ago
add a comment |
@NickAlexeev Sure, done.
– VortixDev
1 hour ago
3
Is every commit to master a stable, tested, quality assured release in your project?
– Alex Reinking
1 hour ago
@AlexReinking Every commit is tested, but I'm just trying to get accustomed to common practices with my personal projects, so it's just me working it and as such there isn't really a system in place other than "make a change, test it myself, commit it".
– VortixDev
1 hour ago
@NickAlexeev Sure, done.
– VortixDev
1 hour ago
@NickAlexeev Sure, done.
– VortixDev
1 hour ago
3
3
Is every commit to master a stable, tested, quality assured release in your project?
– Alex Reinking
1 hour ago
Is every commit to master a stable, tested, quality assured release in your project?
– Alex Reinking
1 hour ago
@AlexReinking Every commit is tested, but I'm just trying to get accustomed to common practices with my personal projects, so it's just me working it and as such there isn't really a system in place other than "make a change, test it myself, commit it".
– VortixDev
1 hour ago
@AlexReinking Every commit is tested, but I'm just trying to get accustomed to common practices with my personal projects, so it's just me working it and as such there isn't really a system in place other than "make a change, test it myself, commit it".
– VortixDev
1 hour ago
add a comment |
1 Answer
1
active
oldest
votes
SemVer concerns versioning releases, not commits. If your version control model happens to require that every commit to master be a release, then yes, every commit will need to be tagged according to the degree of the change.
Generally, though, projects develop a mostly stable product on master and tag the releases they deem worthy of support. When they do so, they will tag according to their versioning scheme, which doesn't necessarily have to be SemVer in particular.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "131"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsoftwareengineering.stackexchange.com%2fquestions%2f388034%2fwhen-should-a-commit-not-be-version-tagged%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
SemVer concerns versioning releases, not commits. If your version control model happens to require that every commit to master be a release, then yes, every commit will need to be tagged according to the degree of the change.
Generally, though, projects develop a mostly stable product on master and tag the releases they deem worthy of support. When they do so, they will tag according to their versioning scheme, which doesn't necessarily have to be SemVer in particular.
add a comment |
SemVer concerns versioning releases, not commits. If your version control model happens to require that every commit to master be a release, then yes, every commit will need to be tagged according to the degree of the change.
Generally, though, projects develop a mostly stable product on master and tag the releases they deem worthy of support. When they do so, they will tag according to their versioning scheme, which doesn't necessarily have to be SemVer in particular.
add a comment |
SemVer concerns versioning releases, not commits. If your version control model happens to require that every commit to master be a release, then yes, every commit will need to be tagged according to the degree of the change.
Generally, though, projects develop a mostly stable product on master and tag the releases they deem worthy of support. When they do so, they will tag according to their versioning scheme, which doesn't necessarily have to be SemVer in particular.
SemVer concerns versioning releases, not commits. If your version control model happens to require that every commit to master be a release, then yes, every commit will need to be tagged according to the degree of the change.
Generally, though, projects develop a mostly stable product on master and tag the releases they deem worthy of support. When they do so, they will tag according to their versioning scheme, which doesn't necessarily have to be SemVer in particular.
answered 1 hour ago
Alex ReinkingAlex Reinking
1,109315
1,109315
add a comment |
add a comment |
Thanks for contributing an answer to Software Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsoftwareengineering.stackexchange.com%2fquestions%2f388034%2fwhen-should-a-commit-not-be-version-tagged%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
@NickAlexeev Sure, done.
– VortixDev
1 hour ago
3
Is every commit to master a stable, tested, quality assured release in your project?
– Alex Reinking
1 hour ago
@AlexReinking Every commit is tested, but I'm just trying to get accustomed to common practices with my personal projects, so it's just me working it and as such there isn't really a system in place other than "make a change, test it myself, commit it".
– VortixDev
1 hour ago