I just upgraded the trunk to rails 1.2.3, thanks to some tips from
James. Seems to be working fine so far. We're moving towards a
release, so while there will definitely be new bugs before then, the
overall trend should be towards more and more stability and polish.
On Mar 29, 2007, at 9:34 PM, James Kebinger wrote:
I switched to trunk for my real data a couple weeks ago and haven't
had any major problems. Certainly no data corruption (thats what
backups are for anyways, right?) the db:migrate went fine after i
fixed one of the migrations and almost everything is working fine
now (the stuff that isn't for me looks to be quirks of the latest
and greatest sqlite3 version)
On 3/29/07, Frederick Alger <[EMAIL PROTECTED]> wrote:
Hello tracks people,
I just downloaded and checked out the Tracks source for the first
time, and as an experiment I upgraded vendor/rails to Rails 1.2.2.
With script/server using mongrel now, my projects page with ~30
projects loads in about a second, where as before it was taking 3-6
seconds with WEBrick. Wow!
So, that said, has anyone gone down this road before, and if so, do
you have any warnings before I corrupt my Tracks database? So far,
all is peachy, and I'm planning on replacing my old Tracks install
with latest trunk.
--
- Fred Alger
@: [EMAIL PROTECTED]
_______________________________________________
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
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
