headers
Johansson Olle E | 17 Aug 13:56
Gravatar

1.6.1 ?

I must have missed something, but I haven't seen any message about  
1.6.1 on this list.

What's the policy for merging stuff now? Did 1.6.0 die and we're  
heading directly towards 1.6.1?

/O

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev
Permalink | Reply |
headers
Sean Bright | 17 Aug 14:52
Gravatar

Re: 1.6.1 ?

Johansson Olle E wrote:
> I must have missed something, but I haven't seen any message about  
> 1.6.1 on this list.
> 
> What's the policy for merging stuff now? Did 1.6.0 die and we're  
> heading directly towards 1.6.1?

1.6.1 is everything that has changed in trunk since 1.6.0 was branched.
 AFAIK, both 1.6.0 and 1.6.1 are feature frozen, and applicable fixes in
trunk are merged to both branches.  New features continue to go into trunk.

The merge process is:

trunk -> 1.6.0
trunk -> 1.6.1

(mergetrunk6 will work with both)

--

-- 
Sean Bright
sean.bright <at> gmail.com

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
(Continue reading)

Permalink | Reply |
headers
Kevin P. Fleming | 17 Aug 16:50

Re: 1.6.1 ?

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.

--

-- 
Kevin P. Fleming
Director of Software Technologies
Digium, Inc. - "The Genuine Asterisk Experience" (TM)

_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--

AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
(Continue reading)

Permalink | Reply |
headers
Johansson Olle E | 17 Aug 17:12
Gravatar

Re: 1.6.1 ?


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
(Continue reading)

Permalink | Reply |

Gmane