Re: Question of the software develpment cycle

Chad <cdalten@xxxxxxxxx> wrote in news:1183083092.367506.97850
@o11g2000prd.googlegroups.com:

This is inexperience. Bear with me.

I recently release a program on sourceforge. However, I noticed that I
made a bonehead coding error. The error doesn't lead to a bug, it just
slows the code down a bit. So, after I correct the coding error, do I
just change the version number from 1.0 to 1.1?

Just curious because I just sort of feel stupid putting in the logs "I
made a correction to the code after someone started to clue me in on
if else flow."

Chad



Versioning is rather arbitrary. Usually you have a "Major.Minor.Fixes"
pattern, but determining where to update the version is a matter of
opinion.

In my personal stuff, I usually work on the next minor revision and
incorporate the bulk of efficiency changes in there. If I notice bugs
after I've released the next minor version, and fix and re-release, I
usually update the fixes verion. For example, my software is currently
version 0.6.1, I screwed up testing 0.6 so bugs got through.

There's another scheme that I'm not too familiar with where the builds
are different and the version number stays the same. Changes to the
codebase (or even builds with no changes?) increment the build number.

Puckdropper
--
Wise is the man who attempts to answer his question before asking it.

To email me directly, send a message to puckdropper (at) fastmail.fm
.