[asterisk-dev] Should ASTERISK-17124 be fixed in 1.8.4.2?

Alistair Cunningham acunningham at integrics.com
Wed Jun 22 08:07:50 CDT 2011


On 22/06/11 20:58, Leif Madsen wrote:
> The reason it doesn't exist is because it was fixed after 1.8.4 was
> created, and 1.8.4.1 and 1.8.4.2 are based on 1.8.4, with only select
> changes made.
>
> Anything resolved after 1.8.4 then becomes available in the following
> RC1 where it is only then pulled from the 1.8 branch directly.
>
> If we just pulled everything in from the 1.8 branch for 1.8.4.2 then
> we'd have many changes that were not directly resolving the issue at
> hand that was triggering the 1.8.4.x release. I think that makes sense
> when you think about it that way.
>
> Basically the only time all changes from the 1.8 branch are pulled into
> a release is at 1.8.x-rc1. Anything after that is a cherry picked issue
> that is justifying an additional release candidate or sub-point release.
>
> Hope that helps,
> Leif.

That makes perfect sense, and had I been thinking clearly I would have 
realised it myself. Thanks for explaining!

Alistair Cunningham
+1 888 468 3111
+44 20 799 39 799
http://integrics.com/



More information about the asterisk-dev mailing list