Release management - best practice

release-management release-cycle
joe picture joe · Sep 25, 2008 · Viewed 10.3k times · Source

I work for a product development company.We first do internal releases,and then public release.I was wondering, how other product developing companies manage their release? How do you give release number? Tag the source control?

Answer

Kevin picture Kevin · Sep 25, 2008

We use SubVersion, where tags and branches are cheap to create.

As far as releases go, we follow this convention:

(Major Release).(Minor Release).(Patch Release).(SVN revision)

  • Patch Release = bug fixes
  • Minor Release = binary compatible / interface compatible
  • Major Release = includes breaking changes.

Does that make sense? If you need more information, add a comment and I'll edit my post to clarify.

Related questions

Getting software version numbers right. v1.0.0.1

I distribute software online, and always wonder if there is a proper way to better define version numbers. Let's assume A.B.C.D in the answers. When do you increase each of the components? Do you use any other …

Read More
Best practices for copying files with Maven

I have config files and various documents that I want to copy from the dev environment to the dev-server directory using Maven2. Strangely, Maven does not seem strong at this task. Some of the options: Simple use a copy task …

Read More
Create a directly-executable cross-platform GUI app using Python

Python works on multiple platforms and can be used for desktop and web applications, thus I conclude that there is some way to compile it into an executable for Mac, Windows and Linux. The problem being I have no idea …

Read More