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

[Gerald (Jerry) Carter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Karolin,

| 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

My only response is that if it is a bug fix credible
for 3.2.1, why not include it in 3.2.0?   I know that
any change involves risk, but these should be low risk
or obvious bug fixes anyways.  Anything that is risky or
questionable should be discussed and reviewed prior to
being checked in.  That is my philosophy at least.

You can always "freeze" the v3-2-test tree a few days prior
to release for escrow.  Just announce that no more
fixes will be pulled into v3-2-stable at that point.
But developers should be confident that every thing in
v3-2-test has been merged to -stable.




cheers, jerry


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIPAF0IR7qMdg1EfYRAm4SAKC14WWy2keCTVOuugWqtFH+JPFI6QCeLTHH
R5F+qbfXuEYpQAa4xz7UAaM=
=wFhM
-----END PGP SIGNATURE-----