When is a Release not a release?

  • Thread starter Thread starter davidanoble
  • Start date Start date
D

davidanoble

Please excuse me if this is not the right forum but I have always been
under the impression that when we made a code change to production,
that was a 'release'. Now one of my new colleagues is indicating that
you can't call a small bug fix a release since a release has more of a
project plan around it. Your opinions are appreciated.
 
We consider a release as being any new revision of software that we ship out
to customers as it has to have its own version number so that we can track
what they're using.
 
I do a lot of work with plugin functionality (system extensibility),
so there is a core application, and a bunch of these plugins that
offer addtional functionality.
Whenever ANY change in code is made available to production (or test
for that matter) it is a release. As a result a version change must
be made (whether it be a minor or major change is dependent upon the
amount of "planning" involved in the release.
 
Excellent point and explanation, thanks Jan.

(e-mail address removed)'s wild thoughts were released on
Mon, 29 Dec 2008 22:09:33 -0800 (PST) bearing the following
fruit:


It will depend on who you talk to.

Would you consider correcting a spelling mistake in a
tooltip a new release?

Marketing certainly wouldn't.

From a development and support point of view, if it goes to
a client it needs a new version number and is a 'release'
however I'd call it a 'maintenance release' of which I make
available each month. Generally it is not required that
clients adopt a maintenance release and many prefer to wait
for a full (major) release.
Click to expand...
 
Back
Top