What should/shouldn't go into v3-4-test

[Volker Lendecke]

On Tue, Mar 24, 2009 at 06:05:18PM -0700, Tim Prouty wrote:
> * Samba4 changes should not go into v3-4-test since v3-4-test is a  
> samba3 release.
> * Franky/merge-build work should not go into v3-4-test.
> * v3-4-test commits should be limited to bug fixes and patches that  
> will help stabilize the code.
> * New feature development and large destabilizing changes shouldn't go  
> into v3-4-test.
> 
> This means that v3-4-test and master will diverge, but it also means  
> that v3-4-test will become a solid release.  Production quality code  
> needs time and testing to stabilize, which is why these release  
> branches exist.  We are doing a lot of QA internally on v3-4-test, and  
> would like to see it continue to stabilize rather than be a quasi- 
> development branch for the next three months.
> 
> Any thoughts?

Full ACK from my side. But it's up to everyone to monitor
the individual checkins and possibly discuss/reject/revert
checkins.

Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20090325/508be538/attachment.bin