version numbering

[Robert Schuppenies]

What should be the name for our next version?
I would suggest 0.2. This would leave us minor numbers (a.b.MINOR)
for bugfixes whereas the first and second number are for major
releases. From my understanding it is okay for major releases to
change the API, whereas minor releases should not.

[Ludwig Hähne]

+1 for 0.2. Most software uses MAJOR.MINOR.BUGFIX, but does not enforce
the "only-major-releases-break-the-API" policy until version 1.0. I
think this scheme would work for us as well.

We will have to decide if we want to release 0.1.1. Up to now, we have
the URI issue because of the unfortunate last-minute migration from
"pympler" to "Pympler" in Pypi. If anything else pops up, I'd vote for a
0.1.1 release (using the 0.1 branch [and properly using svn merge ;)]).

Ludwig

[Jean Brouwers]

My idea was that the next Pympler release would support Python 3.0 and
perhaps some fixes for some of the issues we still have, but nothing
else. In that case, the release could be called 0.1.1 although better
would be 0.2.

My main concern for Python 3.0 support are the package issue and
perhaps exceptions** and str vs unicode vs bytes. It would be best to
handle the Python 3.0 changes now, before any restructuring or other
major changes to the code.

/Jean

**) Python 3.0 requires except Error, e: to be written as except
Error as e: Python 2.6 accepts both and earlier Python versions only
the former.

[Robert Schuppenies]

Jean Brouwers wrote:
> My idea was that the next Pympler release would support Python 3.0 and
> perhaps some fixes for some of the issues we still have, but nothing
> else. In that case, the release could be called 0.1.1 although better
> would be 0.2.

Mh, if we continue at that speed we're soon at 1.0 :)

> My main concern for Python 3.0 support are the package issue and
> perhaps exceptions** and str vs unicode vs bytes. It would be best to
> handle the Python 3.0 changes now, before any restructuring or other
> major changes to the code.

I agree that 3.0 compatibility should be introduced as earlier as
possible. So why not now.

I've created a wiki page to gather ideas of upcoming tasks/features.
Maybe that helps organizing it a bit. You can find it at
http://code.google.com/p/pympler/wiki/ReleaseTasks.