[Biopython-dev] determining the version

[Bruce Southey]

On Thu, Mar 5, 2009 at 6:58 AM, Peter <biopython at maubp.freeserve.co.uk> wrote:
> On Thu, Feb 19, 2009 at 10:25 AM, Peter <biopython at maubp.freeserve.co.uk> wrote:
>>
>> Since this thread last year, there have been no objections.  Following
>> a recent question on the main mailing list about how to determine the
>> version of Biopython this seems worth doing before the next release.
>> Again, an objections or comments on the implementation details?
>> Otherwise I'll make this change shortly.
>>
>
> Changes made in CVS, and updated the release instructions:
> http://biopython.org/wiki/Building_a_release
>
> In between releases, should we leave the __version__ as is, or
> explicitly update it to be something like "1.49+" just after releasing
> 1.49?  This only affects people installing Biopython from CVS, so they
> should be technically inclined...
>
> Peter
>


I agree that it would be helpful to distinguish between an official
release and a build from the CVS. Furthermore, it would then be
important to know when the build from CVS was done at least relative
to the official releases.

So I think you tending to have a numbering scheme like:
1.49 is an official release
1.49+ (or similar) is CVS after the 1.49 official release but before
the next official release 1.50.
1.50 will be an official release
1.50+ (or similar) is the CVS after the 1.50 official release but
before the next official release whatever number it will be.

If so the release instructions should also include an instruction to
change the CVS numbering in the version in __init__.py files after
release has been made.

Also, after looking at the release instructions shouldn't BioSQL and
Doc also have version-related information?
Ideally the Biopython BioSQL code should have some connection to the
main version of BioSQL - I don't use it so it is not an issue for me
(yet).

Bruce