Re: version pinning on tags
Tres Seaver <[email protected]>
| Newsgroups | gmane.comp.web.zope.devel |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephan Richter wrote: > On Thursday 29 April 2010, Baiju M wrote: >>> +1 to use a KGS. ZTK or BB depending on what the dependencies are. >> Since normally we don't pin versions in trunk, I guess we need to >> do the pinning in maintenance branches. Otherwise we can >> keep the version pinning in trunk, but comment the "versions" option. >> Then, just before going for release, uncomment it. >> This will become one more step in creating releases: >> http://docs.zope.org/zopetoolkit/process/releasing-software.html > > Why not leave it always pinned? This way the pinning gets transferred to the > branch/tag automatically. - -1. Trunk development should not be hindered by the need to maintain a KGS of some sort. Testing the trunk against a given KGS should be a separate step from testing against "current" releases. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 [email protected] Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvZki8ACgkQ+gerLs4ltQ5t8gCeMJruyrlLi4ugf0wV2hYq0m0V NdIAoNTugaI4iTHHfI0QWNiJkUBw6ejf =ArEb -----END PGP SIGNATURE----- _______________________________________________ Zope-Dev maillist - [email protected] https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )