> With Tracks, my wishes are a bit unique- run the stable released > version and create my contributions against that. Because I'm using > Track's as my life management system, I want to make sure I'm running > stable code. But to encourage my coding, I'd like to deploy and test > against my real-life environment (a clone of it, with deployment after > testing). To use my changes quickly is a big motivation factor for me, > especially considering my very little free time. If I worked on the > master head, I'd never get to use my changes and still stay on a stable > releases branch.
Interesting. I had the same 'problem' when I started using Tracks. I was running the stable version 1.04x, while there were a lot of interesting features in svn-trunk I'd like to use. Running on trunk seemed a bit risky for day-to-day usage. I tried running both side-by-side to help test trunk. When I felt it was stable enough I switched to trunk for day-to-day usage. (I still do today although I would not recommend it unless you're able to rescue your data if things go wrong :-) ) The issue for tracks is that currently there are not many active developers. This makes that organizing development on a higher level somewhat difficult. I do think we should go for stable branches although it asks for more discipline :-) As to your own development, I would recommend choosing the option that fits best for you. If you like to develop against 1.6, please do. I the changes are candidates for inclusion into Tracks you (we) can just migrate them to the latest master tree for inclusion. Regards, Reinier _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
