Re: [Zope-CMF] Re: SVN: CMF/branches/1.6/ Use GenericSetup 1.2 branch.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 27 Nov 2006, at 11:53, yuppie wrote: Stefan, I don't think this is a legitimate switch: GS 1.2 is *much* later, in terms of release management, than CMF 1.6, and introduces new features. Currently GenericSetup 1.2 is the only version with a maintenance branch. CMF-1.6.1-final was tagged *after* GenericSetup 1.1, so an additional 1.1 maintenance branch would not help us. Therefore using GenericSetup 1.2 in CMF 1.6 might be the best solution. What I really don't like are externals that point to the *HEAD* of a branch. Instead of moving targets we should use revision numbers. (It might make sense to make an exception for CMF trunk.) I'm happy with any policy that we can agree on. Right now there's none, and that leads to confusion. 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. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFastERAx5nvEhZLIRAk0JAJ98gvBRUQ5cdKsOSU6grqlaSMjMigCdFz+T JNqhc3IVZ1O3dI+3EM12Yy8= =qTh9 -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
[Zope-CMF] Re: SVN: CMF/branches/1.6/ Use GenericSetup 1.2 branch.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens Vagelpohl wrote: On 27 Nov 2006, at 11:53, yuppie wrote: Stefan, I don't think this is a legitimate switch: GS 1.2 is *much* later, in terms of release management, than CMF 1.6, and introduces new features. Currently GenericSetup 1.2 is the only version with a maintenance branch. CMF-1.6.1-final was tagged *after* GenericSetup 1.1, so an additional 1.1 maintenance branch would not help us. Therefore using GenericSetup 1.2 in CMF 1.6 might be the best solution. But CMF 1.6.0 was released before 1.1, even:: $ svn propget svn:externals $ZSVN/CMF/tags/1.6.0 ... GenericSetup svn://svn.zope.org/repos/main/GenericSetup/tags/1.1-beta We shouldn't move the 1.6 release line to a newer GenericSetup release, at least without a really good reason. What I really don't like are externals that point to the *HEAD* of a branch. Instead of moving targets we should use revision numbers. (It might make sense to make an exception for CMF trunk.) I'm happy with any policy that we can agree on. Right now there's none, and that leads to confusion. 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. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFauee+gerLs4ltQ4RAsqrAKDZYoUIqwrHe/yDFoj+6vy6wwYIZACgtwsW XT3QZJpUQCj7JaHZWpwEjDs= =CcC2 -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
Re: [Zope-CMF] Re: SVN: CMF/branches/1.6/ Use GenericSetup 1.2 branch.
-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
Re: [Zope-CMF] Re: SVN: CMF/branches/1.6/ Use GenericSetup 1.2 branch.
We use CMF 1.6 branch with GS 1.2 branch in Plone 2.5. This, and itchy fingers, made me update the external. FWIW, when I check out CMF/tags/1.6.2 I expect to get a GS tag as well. When I check out CMF/branches/1.6 I expect to get the HEADs of the respective development branches. Another benefit would be that nightly tests also use branch HEADs, catching discrepancies early on. We use this policy in Plone-world to general satisfaction. Stefan On 27. Nov 2006, at 15:08, yuppie wrote: I'm fine with requiring tagged GS releases for CMF *releases*. But sometimes it is useful to link unreleased CMF branches to unreleased GenericSetup versions. This helps to avoid problems caused by stitching in new versions right before a release. -- It doesn't necessarily do it in chronological order, though. --Douglas Adams ___ 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
[Zope-CMF] Re: SVN: CMF/branches/1.6/ Use GenericSetup 1.2 branch.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan H. Holek wrote: Log message for revision 71310: Use GenericSetup 1.2 branch. Changed: _U CMF/branches/1.6/ -=- Property changes on: CMF/branches/1.6 ___ Name: svn:externals - # # Used for maintenance of external resources in this svn bundle. Edit # this file as appropriate and then run the following command from within # the checkout directory where this file lives on your local machine: # # svn propset svn:externals -F ./EXTERNALS.TXT . # GenericSetup svn://svn.zope.org/repos/main/GenericSetup/tags/CMF-1.6.1-final + # # Used for maintenance of external resources in this svn bundle. Edit # this file as appropriate and then run the following command from within # the checkout directory where this file lives on your local machine: # # svn propset svn:externals -F ./EXTERNALS.TXT . # GenericSetup svn://svn.zope.org/repos/main/GenericSetup/branches/1.2 Stefan, I don't think this is a legitimate switch: GS 1.2 is *much* later, in terms of release management, than CMF 1.6, and introduces new features. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFaf85+gerLs4ltQ4RAiuRAKCRq+M4qyLn3VYN2qH6PH889xSnUwCfaDiL CXXlu6mGIc8tppzEY+whUok= =GkCL -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
Re: [Zope-CMF] Re: SVN: CMF/branches/1.6/ Use GenericSetup 1.2 branch.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Nov 2006, at 21:55, Tres Seaver wrote: I don't think this is a legitimate switch: GS 1.2 is *much* later, in terms of release management, than CMF 1.6, and introduces new features. Stefan, what's the reason for this switch? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFahMARAx5nvEhZLIRAkDLAKCnRtyXQ0/1vT3tpzd1AH26+QmaVgCfaXiu dbGhRuOTqkuFWxgwqcnzDOQ= =ECAb -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
