Quote:
Originally Posted by un_pogaz
Additionally to this fix release, the previous one who has not been published here (v1.4.3) contains three new feature:
https://github.com/kiwidude68/calibr..._check-v1.14.3- Added 'Normalize the fields' and 'Normalize the notes' options for merge and reorder diatrics. (#un-pogaz)
- Added 'Fix Author Sort' action. (#un-pogaz)
- Added Actions Chains support. (#un-pogaz)
|
The version I've released as v1.14.4 in the first post is built on kiwidude's v1.14.3. It should have everything from v1.14.3. v1.14.3 was 'released' in github. If it wasn't previously released here, I assume that was an oversight.
Quote:
Originally Posted by un_pogaz
Else, @JSWolf if I understand your point of view, the one of BetterRed don't come to nowhere either.
So if your publish any hacked version of a plugin in the future, I encourage you to use a exeprimental/preview version number rather that let the official untouched. Like 1.14.3.100. That allow to know that this version is a altered one, and in the same time there is no risk of conflict with the next version when updating in Calibre.
|
I'm going to
strongly recommend against this. The standard plugins is major.minor.micro and stored internally as a list of 3 integer values. Adding a fourth number is outside standard. Unless I missed Kovid blessing that, don't do it.
I also recommend against bumping from v1.14.3 to v1.14.100 as test versions because kiwidude's standard is to increase the micro number for each release. v.1.4.4 would not be called out as a new version if you had v1.14.100 installed.
I could have bumped the new release versions I made to v1.15.0 or v1.14.5 to be higher than JSWolf's versions. I didn't because: a) it's not my repo, so I followed kiwidude's established standard and b) there's no effective difference between (as far as I know) between JSWolf's versions and what I released.