The practice of using multi part version numbers, such as {major}.{minor}.{bug-fix} or {version}.{release}.{minor}.{level}.
1
vote
2answers
42 views
How to version when using trunk based development
I have been reading a bit more about trunk based development, my company currently mainly uses the git flow model, and I had a question regarding the commits that happen on the trunk and how they are ...
2
votes
1answer
56 views
Is it appropriate to convert a project to a different language and keep the same versioning?
Say there's a package, foo. Foo is being developed primarily in Python, up until version 1.13.2. At that point in time, the primary developer decides that Go is much better suited to the task. He ...
-1
votes
2answers
168 views
Why do developers love using code-names instead of actual version numbers? [closed]
99% of software comes in different versions. And quite often developers like naming versions. Example - Android versions:
Froyo
Gingerbread
Ice Cream Sandwich
etc..
It really bothers me because it ...
0
votes
2answers
84 views
How to differentiate versioning between changes on version 1.0 and adding new features towards 2.0?
If I met all requirements on version 1.0 and go on working towards version 2.0, new features would be 1.1, 1.2, 1.3, and so on. What do I version the commits that represent an important fix or a ...
0
votes
1answer
78 views
GitFlow, should my release branch include minor version number?
I've found it difficult to find a definitive answer to this question. Using Semantic Versioning and GitFlow should my release branch include the minor version number? I'm not referring to tags.
My ...
1
vote
2answers
44 views
Update semver minor version on test updates?
I always try to adhere the semver spec when I commit changes. This time though I was wondering what to do when I update my tests: I'm working on an API client that includes a simplified API server ...
2
votes
1answer
71 views
In SemVer 2.0.0, what kind of public API change category is the addition of a new exception?
I am working on an implementation for an existing public API. Now I needed to change the implementation to throw an exception for a failure condition about which previously the API consumer was not ...
4
votes
2answers
88 views
Versioning Apps with SemVer
I've really big problems with versioning my apps. I'm trying to follow SemVer methodology (I'm not sure if it's a methodology or just set of rules).
I've draw a roadmap for my app's versions.
1.0.1
...
2
votes
0answers
71 views
What's the semantic version of the same software for different OS?
What's the semantic version of the same software for different OS ?
For exemple : X.Y.Z
X is a major version
Y is a minor version
Z is a patch
If I have the same version but for 3 different OS; How ...
1
vote
1answer
165 views
Is semver now a standard? [closed]
Is there any reason a new public project being started, if given the choice (e.g., not constrained by their company), would use something other than Semver? Are there competing methodologies, i.e., ...
5
votes
1answer
49 views
Should I treat additional linter restrictions as breaking backwards compatibility?
I'm maintaing a linter library, so this it's basically a set of rules checked against some code one can pass to it. Say, we have rule A which checks some set of cases.
Now imagine that some commit ...
8
votes
2answers
1k views
Does Semantic Versioning allow 4 components in version numbers?
All examples of semantic versioning I've seen show 3 components in use. No more than 2 period characters. At $DAYJOB, we use 4 components in our release numbers:
5.0.1.2
Does Semantic Versioning ...
1
vote
1answer
71 views
Removing old (semantically versioned) NuGet packages
We are running into issues with our NuGet server when we reach 100 packages.
We have multiple packages, all semantically versioned (3 digits), from multiple projects, in our NuGet repository.
What ...
15
votes
5answers
813 views
How to treat bugs that users thought were a feature?
Question:
What is the proper way to address a bug that an end-user thought was a feature?
Elaboration:
I'm guessing that if a large percentage of users expected it as a feature, it should be left "...
2
votes
1answer
121 views
HTTP API Versioning and Need to Introduce Breaking Changes to All Supported Versions
I am developing an HTTP application and deploying this by versioning it against the semantic versioning patterns/techniques/whatever they are. In order not to break existing clients and allow the ...
3
votes
1answer
163 views
In SemVer should I increase the version on every commit/accepted pull request
Running a community project. Have a few pull requests that have been made and the version of our product is currently 2.5.0
All 3 of the changes are feature adds but are backwardly compatible. Should ...
7
votes
2answers
1k views
When and how to do a release?
Scenario
I have a plugin for CakePHP 3, which I am working on and people are submitting bugs for it. I have an active development branch in develop to which I send pull requests from fix branches.
I ...
7
votes
3answers
516 views
Git, semantic versioning and how it fits into (my) a typical development timeline?
I'm working on a Q&A system and about to tag my current application with "1.0.0" for it's first official version/tag. It's about to be rolled out for beta testing to a limited test audience next. ...
2
votes
1answer
102 views
Can tags be used as bookmarks under semantic versioning?
Shameless plug: this question is for StackMode – a StackExchange client for GNU Emacs 24+.
The product I'm working on, version-controlled with git, is a desktop application with an innately exposed ...
19
votes
1answer
2k views
how does semantic versioning apply to programs without API
In http://semver.org/ —which in my perception seems to be the most widely used convention in versioning— it is recommended to increase the major version number when a change that breaks/modify the API ...
17
votes
2answers
6k views
Why is build.number an “abuse” of semantic versioning?
I was explaining a proposed build system (Gradle/Artifactory/Jenkins/Chef) to one of our senior architects, and he made a comment to me that I sort of disagree with, but am not experienced enough to ...
1
vote
1answer
77 views
Is adding support for another operation system a minor version or a patch?
Let's say I use Semantic Versioning for a my project. I'm developing it under FooOS, but the language uses virtual machine(either interpreted language or bytecode based) so any operation system can ...
3
votes
1answer
326 views
Why do we must declare a public API when using semantic versionning?
from semver.org:
Software using Semantic Versioning MUST declare a public API. This API could be declared in the code itself or exist strictly in documentation. However it is done, it should be ...
4
votes
4answers
614 views
How to Name Different Branches with Identical Functionality in Semantic Versioning
For a software, I have two different branches, that only differ in using different library versions of a package, that my software uses. The API of this library has changed between the versions in a ...
2
votes
2answers
196 views
Does Implementing a New Function Imply A New Major Version?
I am currently developing a new library for RESTful web requests in Puredata, and am about to release version 1.0.0. This version will not implement all HTTP verbs, only GET, PUT, POST and DELETE.
In ...
17
votes
2answers
739 views
Semantic versioning when fixing an important bug
I currently manage a library which has a lot of public usage, and I had a question about semantic versioning. I want to refactor one fairly important part of the library which is implemented ...
1
vote
1answer
237 views
Does changing the name of a namespace count as a MAJOR change in semantic versioning?
I'm writing a C++ library, and
according to this site here: http://semver.org/,
I should increment the MAJOR version when I make incompatible API changes.
Is changing the name of a namespace ...
11
votes
3answers
1k views
When should I increment version number?
I didn't learn programming at school and I do not work as a (professional) developer, hence a lot of basics are not quite clear to me. This question tries to clarify one of them.
Now let's suppose ...
3
votes
1answer
139 views
Semantic Versioning and splitting apart a library, providing a bundled build
I've got a nice, fairly popular JavaScript library that is following Semantic Versioning.
The current library has a few dependency libraries, which are available either as separate downloads or as ...
15
votes
2answers
2k views
Semantic versioning for desktop applications
I can easily follow the Semantic Versioning recommendations if I develop a library or API, but what if the developed product is a website or a desktop application?
When would you increment a major ...
1
vote
1answer
133 views
Using <= for every dependency in case of following semantic versioning idea
As Semantic Versioning (and common sense) declares - the major version is incremented in case if non backward compatible change is introduced.
Now let's assume we have a project called Project that ...
5
votes
2answers
296 views
In the context of semantic versioning, does a change in the default configuration warrant a new major version?
My module is enabled by default (i.e. when you add the module). There's also a configuration you can optionally use, which supports an enabled="true|false" setting. This way the module can be disabled ...
