View Single Post
Old 02-23-2015, 07:59 PM   #4
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
It was a "hotfix" not a "new version" so it didn't get a number bump.

I have asked recently for bumping the patch number in such cases, Kovid said:
Quote:
The calibre updater does not check for patch number when notifying for updates, but that change was only made relatively recently so we have to wait till it percolates to most calibre users before enabling patch updates. Also given that only people using distro calibre packages -- a practice I do not recommend or support are affected, I'm not particularly motivated to spend time changing the calibre release automation for them.
I would think it is safe to begin releasing patch versions, since the latest version won't warn about them and old versions will warn about the current major.minor version.

But there is the messing-around-with-automation to deal with of course. Still, I would like it as it enables one to know whether s/he has the updated version, and also allows my linux update script (and *planned* windows/osx port) to sense a new binary version.

Last edited by eschwartz; 02-23-2015 at 08:05 PM.
eschwartz is offline   Reply With Quote