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

On 9/23/10 12:38 , yuppie wrote:
> My goal is to have *one* branch for each CMF version. (Except of CMF 
> 2.1, which has also a non-buildout branch.) I think we have always a 
> primary target platform that is used for development (e.g. Zope trunk 
> for CMF trunk). And some additional supported platforms that are just 
> used for running tests (e.g. latest Zope 2.12 release for CMF trunk). 
> AFAICS it is sufficient to have additional cfg files instead of 
> additional branches for the additional platforms.

+1

jens

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEYEARECAAYFAkybcUAACgkQRAx5nvEhZLJdMACdE2lJlPQsSjKqeLVhA3Npgn0x
FtQAnRN6o30m86QsqMZ+4tva4DA4SRDa
=vMZ5
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist  -  Zope-CMF@zope.org
https://mail.zope.org/mailman/listinfo/zope-cmf

See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests

Reply via email to