When should a commit not be version tagged?2019 Community Moderator ElectionShould a github maintainer...

Could quantum mechanics be necessary to analyze some biology scenarios?

As a new poet, where can I find help from a professional to judge my work?

Is there a frame of reference in which I was born before I was conceived?

Is there a better way to make addon working on both blender 2.80 and 2.79?

How to count words in a line

What am I? I am in theaters and computer programs

When was drinking water recognized as crucial in marathon running?

How to visualize a Cayley graph in this style?

What's the difference between a cart and a wagon?

Can I become debt free or should I file for bankruptcy? How do I manage my debt and finances?

Should I choose Itemized or Standard deduction?

What is the wife of a henpecked husband called?

Contradiction with Banach Fixed Point Theorem

You'll find me clean when something is full

Equivalent to "source" in OpenBSD?

What is this waxed root vegetable?

Hacker Rank: Array left rotation

Linear regression when Y is bounded and discrete

What is the difference between throw e and throw new Exception(e)?

Exponential growth/decay formula: what happened to the other constant of integration?

Why does Starman/Roadster have radial acceleration?

Why does the author believe that the central mass that gas cloud HCN-0.009-0.044 orbits is smaller than our solar system?

How to add multiple differently colored borders around a node?

If nine coins are tossed, what is the probability that the number of heads is even?



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












2















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).










share|improve this question

























  • @NickAlexeev Sure, done.

    – VortixDev
    1 hour ago






  • 2





    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
















2















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).










share|improve this question

























  • @NickAlexeev Sure, done.

    – VortixDev
    1 hour ago






  • 2





    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














2












2








2








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).










share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 1 hour ago







VortixDev

















asked 1 hour ago









VortixDevVortixDev

1195




1195













  • @NickAlexeev Sure, done.

    – VortixDev
    1 hour ago






  • 2





    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






  • 2





    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




2




2





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










1 Answer
1






active

oldest

votes


















9














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.






share|improve this answer























    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
    });


    }
    });














    draft saved

    draft discarded


















    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









    9














    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.






    share|improve this answer




























      9














      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.






      share|improve this answer


























        9












        9








        9







        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.






        share|improve this answer













        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.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 1 hour ago









        Alex ReinkingAlex Reinking

        1,089313




        1,089313






























            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            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





















































            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







            Popular posts from this blog

            迭戈·戈丁...

            A phrase ”follow into" in a context The 2019 Stack Overflow Developer Survey Results Are...

            1960s short story making fun of James Bond-style spy fiction The 2019 Stack Overflow Developer...