17
votes
2answers
508 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 ...
7
votes
2answers
453 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 ...
0
votes
2answers
101 views

Proper name for a project supports 2 different release

Is there a technical name for a software project where the current and prior stable releases are both maintained?
8
votes
1answer
168 views

How to start a new major version of my application, but still keep the old version 'alive'

I have two applications, called A and B. The current version of these applciations are 7.x (some customers run 7.1, others run 7.2, ...). Both applications use a same common framework (let's call ...
5
votes
3answers
499 views

What is your strategy for converting RC builds into retail?

We're trying to implement a strategy for how we transition our builds from RC to released retail code. When we label a build as a release candidate, we send it to QA for regression. If they approve ...
2
votes
1answer
72 views

centralized hosted application framework or “private copies” for each program?

We have a centralised business application framework, and it contains all our business logic and provides access to all our back-end systems. It is accessed by a number of different programs and ...
6
votes
5answers
356 views

Should the build drive your tags or should the tags drive the build?

Our current method of creating a product release is to tag all of our component repositories with the next appropriate version and then modify a master build script with these new version numbers for ...
1
vote
2answers
109 views

Separating Data and Implementation

I'm working on a project that has frequent changes on the database and the implementation layers. I was releasing both the code and the database under the same release version, but since the database ...