Questions tagged [release-management]

The tag has no usage guidance.

Filter by
Sorted by
Tagged with
15
votes
5answers
3k views

A simple ways to improve the release quality in RAD environment

A bit of a background here - we are a small team (of 5) of RAD developers responsible for internal software development in a big non-software company. "Internal software" varies from a desktop .NET ...
11
votes
6answers
16k views

Choosing the right branching strategy for releases

Starting with a new dev team on a new project and we have to define our Branching strategy for our source repository (e.g. Microsoft Team Foundation Server 2010). We've run into a sticky discussion ...
120
votes
21answers
6k views

Is there a way to combat Sales perpetually overcommitting? [closed]

I seem to be repeatedly stuck in a situation where release dates are set not based on anything technical, but because someone in Sales has committed to a customer by then. Based on discussions with ...
152
votes
31answers
26k views

Is it unusual for a small company (15 developers) not to use managed source/version control? [closed]

It's not really a technical question, but there are several other questions here about source control and best practice. The company I work for (which will remain anonymous) uses a network share to ...
24
votes
4answers
7k views

How do you put different versions of your library under version control? Do you use tags? Or branches? Or another method?

I have recently started putting my code under version control (in the lab I'm working, under SVN, and my own codes in github (obviously with git)). Before using version control, I used to do something ...
22
votes
3answers
3k views

Semantic versioning for desktop applications [duplicate]

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 ...
21
votes
2answers
3k views

Is it good practice to store software version numbers in VCS?

A product version, such as v1.0.0.100, represents not only a unique production release of software, but helps identify feature sets and hotfix stages for said product. Right now I see two ways to ...
9
votes
5answers
6k views

How do you handle versioning in a multi-sided project?

I know it's a broad question so I'll try to be as specific as possible. This question is more an "organisational" question than a technical one. We have a multi-sided project with these main ...
10
votes
8answers
11k views

How often to release in Scrum sprint

How often to you release during a sprint. Only at the end of the sprint or every time a feature is ready. And how to you handle bugfix releases?
7
votes
7answers
2k views

How should semi-agile team operate during management-imposed waterfall-like “testing phase”

I'm not looking for advice how agile process should work. I know that part. I'm curious what the best way to adapt the process to a typical large, well-established corporation who loves its "processes"...
16
votes
5answers
3k views

What is a realistic way to handle customer-specific software patches?

I'm trying to gather effective ways that others have solved the following problem. At work we've been forced to release a software patch (to be installed on end-user systems) that we only want ...
3
votes
3answers
289 views

Differentiate between snapshots and official releases, while deploying exactly what has been tested

Suppose the following situation: A CI server generated regular snapshot artifacts At some point, an artifact is considered "stable" and is given to QA for testing If it passes, it's deployed as an ...
2
votes
1answer
153 views

Formulate release notes consistently

In my project, I came across understanding that writing release notes is both helpful and necessary. However, it is not required by my management and I keep these files virtually to myself. You could ...
6
votes
3answers
1k 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 ...
7
votes
1answer
999 views

What's the best way to acknowledge many FOSS sources in a single project?

I have a project which uses a large number of LGPL, Artistic and other open-source licensed libraries. What's the canonical (i.e. the "standard") way of acknowledging multiple sources in a single ...
3
votes
3answers
603 views

Release Planning in Agile/Extreme Programming

I've been studying couple of books of how to exactly implement agile. I am confused about release planning. Our application is a Insurance System consisting of different modules (Quoting, Policy ...
1
vote
2answers
1k views

Looking for good practices on managing branches and developers in Git [duplicate]

I a little while ago I joined a new development team and recently we had our first major release. We've used Git since the beginning of the project and by now are somewhat comfortable with it. However,...
1
vote
2answers
164 views

Applying hotfix to intermediate commit on master

Below is the Gitflow workflow followed, where master branch has the commit history(git tag) of different releases. From release mgmt aspect, we are deleting the release branch after merging with ...