Ah ok. So let's see if I got this right: Even though we might be calling it 0.2.1, we can still use trunk for the release. So the version number is just a semantic to indicate if it is a minor or major release. (The latter typically introducing major features or incompatibilities). 0.2.1 does not necessarily reflect a release branched from a specific release, in this case the 0.2 tag. (Although it *could*). Correct me if I'm wrong.
On Tue, Jul 24, 2012 at 12:19 PM, Ioannis Canellos <[email protected]>wrote: > 0.2.1 or 0.3 really depends on what we are going to ship. If we are just > shipping the improvements of our existing modules, then I say it should be > 0.2.1. > If we are going to give the gsoc stuff to the world then it should be a > 0.3. > > -- > *Ioannis Canellos* > * > FuseSource <http://fusesource.com> > > ** > Blog: http://iocanel.blogspot.com > ** > Twitter: iocanel > * >
