On Apr 4, 2006, at 4:51 AM, Tommi Hassinen wrote: > So, my idea is that you could freely do the changes you like to the > VERSION_2_BRANCH, and then we release it as v2.0 when you think > it's ready. I'm focusing on HEAD version, and try to do tasks that > help us longer term. Since VERSION_2_BRANCH and HEAD look the same > from the user's perspective, we can later release HEAD as v2.10 or > v2.20 when the time is right. Well, I'm certainly willing to "take over" for v2.0. If Donald would like to join me, great! One thing I'd like to do is make a VERSION_2_BRANCH for libghemical too. I know Tommi assures me that libghemical HEAD won't break things, but I think it's safer and can let Tommi and others change libghemical HEAD without worrying about breaking things. I'd also like to suggest that we add Donald as a member of the project at bioinformatics.org so that he has CVS write access -- he won't have to constantly send patches to the list. :-) > Let's just solve the issues like Å/nm and configuration dialog so > that the version jump would be as small as possible. I don't think a version jump matters much. Many users seem to think 1.0x is the current release, so I personally don't think it matters whether HEAD becomes 2.1 or 3.0 or Ghemical MegaServer 2008. (Ha!) What I think is important is that we have some longer-term plans, think about what sorts of changes we'd like to make, and if needed to make branches before any sort of huge source changes. After all, the next few releases are likely to come from the VERSION_2_BRANCH, e.g. 2.0.0, 2.0.1... Cheers, -Geoff