[asterisk-dev] Confused with release numbers, how to manage incremental patching ?

[Pavel Troller]

> Pavel Troller wrote:
> 
> >   My question is: What will be the next base of the "regular" patch (i.e.
> > 1.6.1.9-rc1, as announced) ? Will it be 1.6.1.8, or 1.6.1.7-rc2 ? If the later
> > is true, I can safely skip the .8 patch, because I'm not caring about the
> > problem (not using ACLs in SIP). But if the first is true, what I'm supposed
> > to do ? Unpatch to the pure .6, then patch to .8 and then patch with .9-rc1 ?
> > Will it contain all the changes contained in .7-rc1 and .7-rc2 ? I'm really
> > confused by this strange numbering... 
> 
> It's not strange numbering, and it was clearly documented in the release
> announcement.
>
> Kevin P. Fleming wrote:
>
> The answer to your direct question is yes, the 1.6.1.9-rc1 patch will be
> against 1.6.1.8, since that is the previous release. It will contain all
> changes in the 1.6.1 branch since 1.6.1.6 was released, which will
> include everything that was in the 1.6.1.7 release candidates, the
> security fix that went into 1.6.1.8, and any further bug fixes committed
> since 1.6.1.7-rc2 was released.
> 
Hmm...
  I've just downloaded 1.6.1.10-rc1 patch and it is against 1.6.1.7-rc2! So,
I've just skipped 1.6.1.8 and 1.6.1.9 and the patch applied (almost) cleanly
to my 1.6.1.7-rc2 sources! Perfect! But I'm even more confused than before,
because it totally differs from your explanation. So, is it generally always
as now, or is the 1.6.1.10-rc1 patch an exception to your rule ? (BTW, I've
found a small mistake in your explanation, because you write that 1) it will
be against 1.6.1.8 and 2) it will contain the security fix for 1.6.1.8, which
can't be simultaneously true, because the patch would not apply then :-) ).

  With regards, Pavel Troller