[asterisk-dev] 1.6.1 ?

[Johansson Olle E]

17 aug 2008 kl. 16.50 skrev Kevin P. Fleming:

> Johansson Olle E wrote:
>
>> What's the policy for merging stuff now? Did 1.6.0 die and we're
>> heading directly towards 1.6.1?
>
> Nope, this is the new release management policy as previously  
> outlined.
> Now that 1.6.0 has reached release candidate status (with tarballs  
> to be
> released tomorrow once the latest Zaptel release passes some testing  
> in
> Digium's PQ lab), 1.6.1 has been branched and is feature frozen.
>
> Now that 1.6.0 has reached 'rc', the only changes it should receive  
> are
> for bugs that are regressions in that release or are for serious
> (critical) or security problems. 'Regular' bug fixes should be put  
> into
> trunk and 1.6.1. There is no need to 'block' these revisions in the
> 1.6.0 branch, because nobody is ever going to run an 'svnmerge  
> avail' to
> pull stuff from trunk into 1.6.0.

Thanks for the information. There could, of course, had been an alert
of this milestone being reached to the mailing list :-)

/O