Tony Meyer <[EMAIL PROTECTED]> wrote:
> > I just need
> > to figure out what to generate in the version.cfg for the
> > "Outlook" and "POP3 Proxy" sections so that existing 1.0.x
> > versions will be able to update properly when 1.1 is released.
>
> Good point - although we could always change the
> I just need
> to figure out what to generate in the version.cfg for the
> "Outlook" and "POP3 Proxy" sections so that existing 1.0.x
> versions will be able to update properly when 1.1 is released.
Good point - although we could always change the download page value so that
1.0.x looks in a d
Tony Meyer wrote:
>> It doesn't support the
>> "1.0rc2" release candidate format, but that shouldn't take
>> more than a couple of minutes to add.
>
> We could switch to just "c" (which is nice, since it's then 'a', 'b',
> 'c') and we'd then match the Python distribution itself. In that
> case, t
> As long as we have only one version, I think a lot of this
> could be stored once in the main "spambayes" package
> __init__.py file and eliminate all the duplication.
+0.
> distutils has a StrictVersion class which parses a version
> string similar to what we use with versions of the form
Tony Meyer wrote:
> [Kenny, way back in February]
>> My proposal is that all apps share the source release version
>> as their primary version number. The shared release version
>> would consist of the following parts:
>>
>> * A major/minor version number (1.0)
>> * A release number that would in
