> Dave> what are the CVS tags identifying 1.1a4 and 1.1a3? > I can't find > Dave> them. > > That's because the bozo (that would be me) failed to create > them when I > created those releases. My apologies. I will try to > remember that next > time.
There is also the issue that a bozo downunder had a number of changes he checked in *after* skip's initial email, and yet more changes that weren't even identified until I tried to put my package together... so in this case at least, the lack of a tag is a good thing, otherwise we'd be forced to brand my binary 'a5' or similar. The way things stand at the moment, we can pick some date in the future, nominate that as the *real* a4, make a tag and binaries, and forget about it for another few months (that is assmuming we can consider Skip's build 'release 1.1a4 beta 1" or something painfully convoluted...) Sadly, I fear my email about the binary scared too many people off - I'm yet to receive a single confirmation that the binary package works for someone. Oh well - I suggest that we just wait a few more days, then re-package a4 and release it anyway (and make a tag at that point). In private email I've been told that a number of the links in our docs and on the web site are broken, which I'll try and address, or if that fails, forward details here... Cheers, Mark _______________________________________________ SpamBayes@python.org http://mail.python.org/mailman/listinfo/spambayes Check the FAQ before asking: http://spambayes.sf.net/faq.html
