[Gnumed-devel] Gnumed-update

[Jim Busser]

On 11-Aug-09, at 2:24 AM, Karsten Hilbert wrote:

<People> should most definitely be running v10.8 or else...

If 10.0 is being used only for evaluation, a failure to update maybe only gives a suboptimal impression of GNUmed.

Even so, updating of the server / database (for bug fixes) remains highly desirable, both for evaluation but *especially* in production.

Two ideas come to mind if we want GNUmed database managers to stay aware of the updates:

1. In order that update messages not be buried inside devel messages, at what point should we re-activate address@hidden which still has 70 people subscribed? Maybe that is where we should be sending future updates (which we can still cc to devel with the reminder to subscribe to gnumed-update)

2. Whether it is feasible for "Check for updates" to communicate not only the existence of an update, but its "criticality". Could any such criticality be made apparent through the checking for and communication of a new client?