I don't know when my ISP will upgrade to rails-2.0. If I were them, I'd wait a couple releases to see if there were any security issues first. So yes, release early and often and in managable chunks.
Taybin On Oct 1, 2007, at 8:12 AM, "Nicholas Van Weerdenburg" <[EMAIL PROTECTED] > wrote: > > On that topic- are their performance improvements slated for Tracks > 1.5? > > On the release schedule, I agree with the though- ASAP unless > performance improvements warrant Rails 2.0. > > > Thanks, > Nick > > -----Original Message----- > From: [EMAIL PROTECTED] on behalf of > Steven van Dijk > Sent: Mon 10/1/2007 9:24 AM > To: [email protected] > Cc: > Subject: [Tracks-discuss] New features, committers,and a new > version of Rails? > > Hi, > > > On 10/1/07, [EMAIL PROTECTED] < <mailto:[EMAIL PROTECTED] > > [EMAIL PROTECTED]> wrote: > > My question to the group is: should we upgrade to Rails 2.0 before > the Tracks 1.5 release? > > > I would advise you to postpone the upgrade until after Tracks is > released. Try out all the new features, rigorously clean up the > code, make the trunk as unstable as you want. Right now I think lots > of people are eagerly awaiting the release and I think you should > remain focussed on that. The only valid reason I can think of to > upgrade would be a significant performance improvement. Tracks is a > terrific GTD tool but it would be nice if it were a bit snappier. > > Just my 2 cents... > > Bye, > Steven > > > > > > > _______________________________________________ > Tracks-discuss mailing list > [email protected] > http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss _______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
