As you all have seen, Solfege development have been really slow lately, but now I think we should be back on track again.
I uploaded a devel release (3.21.3) yesterday and I am now adapting a solmisation dictation module I got from Axel Chr. Schullz. When that is committed, I will release 3.21.4, do some testing and make a new stable release. Then I will start using git for version control instead of bzr. I will do a fresh start by adding 3.22.0 as is, and not trying to convert the bzr repository to git. Converting from tla to baz to bzr created enough problems, so I don't want to go through that once more. After moving to git, solfege will be ported to Gtk+ 3, so we will not loose much by not converting the archive. New gtk+ api will mostly stop us from backporting new code anyway. I will keep the bzr repository at www.solfege.org/bzr. So the 3.23.x devel branch will be used to stabilize the gtk3 port and do some code cleanup. Then, after a usable 3.24.0 running on gtk+3 is released, I have to decide if I should work on new exercises or port Solfege to Python 3.3. Why git? People have asked for it. Git is maintained. Bzr developement have stopped. Git looks much nicer than last time I looked, several years ago. Learning new things is fun. -- Tom Cato Amundsen <[email protected]> http://www.solfege.org/ GNU Solfege - free ear training http://www.gnu.org/software/solfege/ ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Solfege-devel mailing list To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe", or visit https://lists.sourceforge.net/lists/listinfo/solfege-devel
