gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] versioning scheme


From: James Busser
Subject: Re: [Gnumed-devel] versioning scheme
Date: Tue, 23 Sep 2008 22:53:26 -0700


On 23-Sep-08, at 10:21 PM, Gour wrote:

The plan is simple:

Good ideas except to figure out

1) the database format should be kept unchanged for the same major
releases, i.e. 0.3 series should keep the same format (e.g. 0.3 release, 0.3.1, 0.3.2 etc.) If the format has to change, it calls increasing the major release (e.g. to 0.4) and it means that only minor fixes should go
into minor release

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


2) database format has to be 'in sync' with major release, so instead of
v9, v10, there should be v0.3, v0.4 etc...

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

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

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




reply via email to

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