Am 29.09.2017 um 12:16 schrieb Graham Leggett:
On 28 Sep 2017, at 7:10 PM, Helmut K. C. Tessarek <[email protected]> wrote:
I have a question. Why are you tagging a release and do testing? Most of
the time a problem is found and a new release is tagged and it starts
over (I think the max was a 3 or 4 patch level jump).
Why not tagging an RC? People test the RC. When all is ok, the RC is
released. If not a new RC is tagged.
Because version numbers are cheap. If you call it RC, or call it the next patch
version, it doesn’t ultimately matter
it's not about cheap - it's just questionable that after 2.4.12 the next
release is 2.4.16 because it looks not really sane
* Fr Jul 10 2015 Reindl Harald <[email protected]>
- update to 2.4.16 (2.4.13, 2.4.14 and 2.4.15 was skipped upstream)
