-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 27 Nov 2006, at 14:26, Tres Seaver wrote:
I'd suggest a policy where a CMF maintenance branch points to the
head of a GS maintenance branch, and when a CMF version is tagged its
external is "frozen" at that particluar SVN revision for GS. There's
no need to make a GS tag for a CMF release I think.
I think we should be *trying* to keep the CMF pointed at released
versions of GS, and should definitely delay making CMF releases
until we
can tie them to a tagged release of GS. Dependencies which are
released
separately need to be managed with more care.
That policy is great, too. We just need to make sure to cut GS
releases whenever we think we need new GS features in the CMF that
only exist on GS branches or the GS trunk.
So far the release frequency for GS has been very slow, it might need
to speed up a bit for this policy to be effective.
jens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFaulFRAx5nvEhZLIRAp5mAKC1NmSYBBRUokXPCx82CG6qSIvQVwCfQl/J
9/uKFxZ35SCdz2O9KNgNLis=
=zdDO
-----END PGP SIGNATURE-----
_______________________________________________
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See http://collector.zope.org/CMF for bug reports and feature requests
