Quote:
Originally Posted by DrChiper
What I miss in the above discussions is how to guarantee that the community code changes find their way back in the main branch of of the source code of the original developer/maintainer. When that developer/maintainer has already made changes without some official release yet, how can we make sure the temporary community fixes do not get lost or even break existing code?  |
The short answer, IMO, is there are going to be no guarantees.
Calibre plugins are informal, volunteer development, without uniform methodology. It's a hobby, not a job.
My personal takeaways are:
- Continue with 3 number only versions. 4 might appear to work, but it's untested and unapproved.
- Bump at least the minor (vs micro/patch) number for plugin releases and use micro/patch number for unofficial and test versions.
Basically, what I've already been doing. So no surprise I like it.
I should have handled the versions for ME/QC/GrS better; that's on me. It was more of a mistake in haste than a conscious decision. However, I don't think it's a big enough deal to go bump and release again.
While I agree with BetterRed in general that superseded plugin zip files should be removed, I don't see it as a 'report to mods' offense.
For example, JSWolf PM'd me about releasing his version of
Hyphenate This! (OP appears MIA) and my first thought was to save the prior version in a post, since there's no source repo link.