[SCM] Samba Shared Repository - branch v3-0-test updated - release-3-0-29-4-gcf9ef3a

Karolin Seeger ks at sernet.de
Tue May 27 06:31:42 GMT 2008


On Mon, May 26, 2008 at 10:03:04AM -0700, Jeremy Allison wrote:
> Yeah :-). Most new development goes into 3.3,
> that branch has nicely separated out the new
> features problem.
> The fixes that go into 3.2-test people assume
> will be in the next 3.2 release.
> My vote would be to automatically pull 3.2-test
> into release without explicit notification.
> No one should be doing new feature/experimental
> work in that branch anyway, just bugfixes.
> Having the explicit notification step just
> allows people to forget.
Ok, that is a possible solution, too.

From my point of view, it would be very nice to have double checks of all
patches which might go into v3-2-stable now. The main advantage of the
notification is that developers can argue why this one should go into the
final release (and I want arguments now! ;-). But of course it is possible 
to ask them before pulling the patches, too.

But there is another point:
I would have the chance to put patches which should be included in
3.2.1, but not in 3.2.0 in v3-2-test. Testing would be much easier then...

To clarify:
v3-2-stable: 3.2.0rcX, final 3.2.0
v3-2-test:   upcoming 3.2.1
v3-3-test:   3.3.0

Do you agree?


SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.SerNet.DE, mailto: Info @ SerNet.DE

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
Url : http://lists.samba.org/archive/samba-technical/attachments/20080527/d8d5be07/attachment.bin

More information about the samba-technical mailing list