Hi Jörg, On Mon, Jan 20, 2025 at 09:38:24AM +0100, Julien Plissonneau Duquène wrote: > Le 2025-01-20 08:03, Jörg Frings-Fürst a écrit : > > > > Is it enough to change from 1.0.14-19 to 1.0.14-20+git[commit id]? [...] > 2. if the changes are extensive and you would rather repackage the whole > source tree from git, then 1.0.14+git[date . commit id]-1 is appropriate.
Since upstream is friendly and supportive of downstream (https://gitlab.com/sane-project/frontends/-/issues/33), would it be worth considering asking the maintainers if it would be more appropriate to number your git shapshot with 'pre-release versioning' backwards from the next version? (I thought I saw a suggestion from him that it might be time for a release soon but that might be backends and I can't find it now! It might be that your enquiry prompts him to release anyway to roll up fixes that have accumulated.) If a new release is imminent then this style would be more representative to users of what they were getting and then when you update to their eventual release it would be a tidying up exercise with a small delta (hopefully in time for trixie)! :-) e.g. 1.0.15~git20241023.5c148771-1
