[Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. I'll agree -- I don't want the trunk to have *any* version number in it, because I don't want anyone to even think about doing a release from the trunk. It wouldn't need changing, either. Tres. - -- === Tres Seaver +1 540-429-0999 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHLcY4+gerLs4ltQ4RAukVAJ9OOGbHUUf5MEN6hia7tKu2y4gdSQCgy1rb e44xwJPeWLzZUtyX2CupBO0= =ReTA -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. I'll agree -- I don't want the trunk to have *any* version number in it, because I don't want anyone to even think about doing a release from the trunk. It wouldn't need changing, either. I'd like that too, but it breaks the expectations you'd have about the development egg that's defined by a trunk checkout. It needs a meaningful version number to satisfy version constraints like z3c.foopkg=1.3. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
On Nov 3, 2007, at 4:24 PM, Philipp von Weitersehausen wrote: Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. As far as I see (and apparently Jim, too, since he agreed to use this policy) it's the best compromise between - making sure that nobody creates releases from the trunk (hence the dev marker) - giving development eggs from the trunk or a release branch a *meaningful* revision number (hence the version bump you find so silly) Consider this an edict. (Not if I can just remember to add dev) Thanks for putting this together, Jim -- Jim Fulton Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
From the check-in messages: Changed: U zc.i18n/trunk/setup.py - version = '0.5.2', + version = '0.6.0', As best I can tell, http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/releasing-software.txt was accepted as policy (Jim endorsed it and no one maintained public objections). Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. -- Benji York Senior Software Engineer Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [Checkins] SVN: zc.i18n/trunk/setup.py vb
Stephan Richter wrote: On Saturday 03 November 2007, Benji York wrote: Therefore, anyone editing the trunk version numbers needs add dev (no hyphen) on the end. Thanks. I just reread Jim's edict E-mail about the topic and noticed that I indeed missed the dev postfix. That changes nothing about the fact that I still think this is totally silly. As far as I see (and apparently Jim, too, since he agreed to use this policy) it's the best compromise between - making sure that nobody creates releases from the trunk (hence the dev marker) - giving development eggs from the trunk or a release branch a *meaningful* revision number (hence the version bump you find so silly) Naturally I'm willing to listen to alternative suggestions. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
