[Tahoe-dev] next release (imminent!) -- version numbers

[Brian Warner]

> You mentioned that we should release "0.3.1", but the convention is that a
> release which adds functionality should have a new minor version number, so
> the next release should be "0.4.0".

Yeah, that works for me. Another convention we might wish to establish is
that we spin the minor number each time we break compatibility with the
previous release, and the new directory-node stuff certainly does that. At
this point in the development cycle, it's unlikely that we'll make a lot of
releases with micro_version != 0, but that's just life on the edge. As long
as we're comfortable with things like 0.142.0, this is a fine policy.

0.4.0 it is.

cheers,
 -Brian