On 7 May 2007, at 18:28, Nicholas Van Weerdenburg wrote: > I'm a new user of Tracks, into day 3 of my usage. I'm quite impressed, > and like the design sensibilities.
Glad you're enjoying it. > What are the experiences or recommendations regarding running on 1.050 > or 1.10? First, there is no 1.10 yet - that's the milestone for after the next release. The trunk version will eventually be 1.050 when it's released as a stable version. The standard scary boilerplate for working with trunk is: 1. It's not a stable version, and it changes frequently, so I wouldn't advise using it for a 'production' setup. If you do decide to risk it (as some here have), PLEASE make sure that you make frequent backups of your database so that you can start from scratch if things go wrong. 2. Please don't run it on a shared server: it *should* be stable, but it's not responsible to run it on a shared server when it might just start eating RAM and make you very unpopular with your server neighbours. 3. Please submit bugs on Trac when you find them. This moves development forwards quickly. > My context: > -I've installed and have been running 1.043 on Textdrive for three > days > now. > -I've significant ruby, rails, and textdrive experience It's fine to run 1.043 on Textdrive, but please don't run trunk on the shared servers (see above). > -I don't mind a few issues, but this is intended to be my main task > management system, running about 120 projects and 400-500 tasks. See above. By all means, play about with trunk, but I really wouldn't use it as a production system unless you're prepared to spend a bit of time reinstalling things if it breaks. > I noticed in my days using Typo, many people ran on the trunk. Is > that a > common practice with Tracks? I try to discourage it, but people wilfully disobey me! > Also, what is the philosophy behind having a 1.050 and 1.1 branches? 1.1 isn't a branch yet. It's just a convenient way to separate out feature requests into things that will be in the next release or some release after that in the bug tracker. > Final question- how are people using the RSS feeds? As this is likely > the main task manager for a person, what need is there for > aggregation? As others have said, it's often a good way to pick out particular categories of task. I personally use a text feed for things due this week, and have it emailed to myself early each morning via a cron job. Then I have a reminder of due tasks in my email client every day. cheers, bsag -- but she's a girl - the weblog of a female geek http://www.rousette.org.uk [EMAIL PROTECTED] _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
