gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnumed-devel] Re: versioning scheme


From: Gour
Subject: [Gnumed-devel] Re: versioning scheme
Date: Wed, 24 Sep 2008 08:22:20 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux)

>>>>> "James" == James Busser <address@hidden> writes:

James> what client versioning number means to users. 

What database format means to users :-)

James> Presently it is the 0.3 level (first decimal place) which is the
James> major version thus a forcing up to 0.4 implies a major
James> enhancement to what the client can do when the needed database
James> change only enabled something small like non- mandatory date of
James> birth

Breaking format of the database is, imho, of major concern no matter how
big/small the change is.

To do it less often, it means more time has to be spend planning future
releases. 

Take a look around and you will see that breaking of 'API' does not
justify 'minor-upgrade' only.

James> the scripting presumably parses whole numbers to the right of "v"
James> and if there are people however few already in production with
James> v<whole
number> it may be an impossibility to change to v_0.4 without a lot
James> of manual work. This should wait for some extra discussion.

There is some way for sure, and scripts can be changed. It's better,
imho, to spend time fixing the scripts than to continue confusing
end-users.

James> If it might help, I have added database version info to the page

James>  http://wiki.gnumed.de/bin/view/Gnumed/ReleaseStatus

Let's hope we'll get rid of this info in the future ;)


Sincerely,
Gour

-- 

Gour  | Zagreb, Croatia  | GPG key: C6E7162D
----------------------------------------------------------------

Attachment: pgpoLpPPAV5xE.pgp
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]