On Jun 28, 2006, at 11:28 PM, Phillip J. Eby wrote
...
>> It isn't my intention to provide daily builds. I just happen wanted
>> to make
>> quick and dirty releases while stuff is new. These are like alpha
>> release, but I'm
>> leveraging the revision tagging to automate generation of release
>> numbers.
>
> Hm. Well, different strokes for different folks. I prefer to bump
> the alpha or beta number, since a short number is easier for humans
> to refer to; it's annoying to have to ask if someone has 0.6a9dev-
> r19684, versus something like 0.6a9snap3. The latter can be done
> with tag_build='snap3' in your setup.cfg, modulo the "register"
> issue we've already discussed.
>
> But of course your practices are up to you; I just mention this as
> an idea to make communications about your projects a little easier,
> at the cost of editing setup.cfg (or overriding --tag-build on the
> command line) when you do a release.
I'm happy to get input.
1. If I'm going to edit setup.cfg, I might as well edit setup.py
2. A reason I want to automate this is a feat that I'll forget to
edit setup.py
or setup.cfg and overrite existing releases (or fail to do an
update without
realizing it because the existing release doesn't get overwritten.
Another issue is that I see us moving toward lots of fairly fine-grained
packages and I want to keep the ceremony pretty low.
Jim
--
Jim Fulton mailto:[EMAIL PROTECTED] Python
Powered!
CTO (540) 361-1714
http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org
_______________________________________________
Distutils-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/distutils-sig
