Re: [Gnumed-devel] Gnumed-update

[Jim Busser]

On 12-Aug-09, at 4:12 PM, Jim Busser wrote:

I keep forgetting to post release notices to -update. We should be

doing that even now.

Release notices for the release candidates should likely be constrained to the -devel list, yes?

Release notices for official releases have the disadvantage that at the point of first availability (and potential announcement) they are really only available as tarballs.

I wonder therefore whether announcement on gnumed-update should be delayed until the first package (typically debian) becomes available to users. Subsequently, within that release, any availability of an update for one of the other distributions could be sent.

I really like out current Downloads page http://wiki.gnumed.de/bin/view/Gnumed/InstallerGuideHomeShort but do we care that the "latest version" applies only to the tarball until it has been made available for one or more distros. Maybe we can just append "(Debian)" as below

Latest Version: Client 0.4.6 / Server v10.6 (Debian) ‒ June 18, 2009

Also, I notice that we already require, to manually update, for each target distribution, the target package for the "tree download" button.

This leaves the liability to fail to redundantly update the links on the page

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

so maybe I will just revert those to the branch directory and not the individual packages.