Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 8B6C662698E for ; Mon, 16 Apr 2012 17:54:04 -0300 (ADT) Received: from mail-qc0-f174.google.com ([209.85.216.174]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1SJsvz-0004B8-Bp for pgsql-hackers@postgresql.org; Mon, 16 Apr 2012 20:54:04 +0000 Received: by qcro28 with SMTP id o28so3419150qcr.19 for ; Mon, 16 Apr 2012 13:53:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=YfJrYlEOZSI1Ipw3dmuCDYg/F7WI7KhMhFr3Jm8ntaU=; b=JSVNPpceEWEEcR65mdSmU6Dx7uB69WPrAfgi6K3e+a1EhmGpUR1wFmuNHtOArMKlia 0f05B/ft9uzAe6Rvt04gqdOZJDIecIeqcbodaX0H38A+lgbTzB33eVHg36jr6JlrTGWs /N1lFoUe9jbdFKNjXw1+2FxDbJil+btfG4N/gDemL3TiyTWZUdlFzAZ74gOj4eES1n6l Yl24isg8OECmZiYyvT9DFJRVptNonVJKwnrNMKQUY0rxUtrnPJVZqGd6S+/qUNXrqx9z 8h8AnukJnUq8PoZAIwiwmq4DRMEO1v0TbFIt0SFSm1hOEG/woNJQxQC+/iqW8mIK1e5w kllA== Received: by 10.229.154.78 with SMTP id n14mr3533671qcw.119.1334609630291; Mon, 16 Apr 2012 13:53:50 -0700 (PDT) Received: from speedbook-air.home.jay.fm (home.jay.fm. [173.166.48.118]) by mx.google.com with ESMTPS id ha3sm36247683qab.13.2012.04.16.13.53.47 (version=SSLv3 cipher=OTHER); Mon, 16 Apr 2012 13:53:49 -0700 (PDT) Message-ID: <4F8C86D9.4060008@gmail.com> Date: Mon, 16 Apr 2012 16:53:45 -0400 From: Jay Levitt User-Agent: Postbox 3.0.3 (Macintosh/20120304) MIME-Version: 1.0 To: Alex CC: Peter Eisentraut , Robert Haas , Tom Lane , Greg Smith , pgsql-hackers@postgresql.org Subject: Re: Last gasp References: <4F83FCB10200002500046D70@gw.wicourts.gov> <4F84D3A0.8010808@2ndQuadrant.com> <1334165303.25392.9.camel@vanquo.pezone.net> <28338.1334168965@sss.pgh.pa.us> <1334180206.25392.39.camel@vanquo.pezone.net> <1334350086.9019.16.camel@vanquo.pezone.net> <878vhyeqyq.fsf@commandprompt.com> <4F89ED6C.4030609@gmail.com> <87d379mwan.fsf@commandprompt.com> In-Reply-To: <87d379mwan.fsf@commandprompt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201204/846 X-Sequence-Number: 206649 Alex wrote: > Jay Levitt writes: > >> Alex wrote: >>> I didn't follow this whole thread, but have we considered Redmine[1]? >> As the resident "Ruby is shiny, let's do everything in Rails on my >> MacBook" guy, I'd like to make a statement against interest: I've >> tried Redmine a few times and it's been painful. Much of the codebase >> is deprecated, it's slow, it has no meaningful search (in 2012?!), >> I've seen wiki edits disappear, and at the moment pulling up its own >> FAQ page at redmine.org times out. > > Yay, that's totally FUD to me. You're right, it was. My bad. Someday I will find the balance between precision and concision. > Could you please elaborate a bit on your points? > > Deprecated codebase? Let me guess... > > It runs on an outdated version of Rails (2.3) but only because Rails is > changing so rapidly, I believe. There is work in progress[1] to move to > the supported branch Rails-3.x. I wasn't even thinking of that; I know many production systems still run on Rails 2.3, and in fact it probably even performs better for some workloads. 3.x is a mixed bag. I don't hold that against Redmine. But it's still FUD, because I can't remember where I saw this information. So: withdrawn. > > Slow? Do you have any data to back this point up? No measurable data; just a sigh of relief when switching from Redmine to Github - and GitHub ain't a speed demon. In general, I've seen multi-second page load times on crazy-simple things like wiki edits; this was on a hosted provider (sourcerepo.com), but they also hosted our git repo and we had no speed problems there. > No meaningful search, eh? Works for me. Redmine searches return partial-word matches, and there's no way to disable that. Searching for "test" finds "latest". To me, that's broken. Also, the UI is very 5 years ago; e.g., "compare revisions" uses the same columns-of-radio-buttons approach as MediaWiki. If the goal is a tool to reduce friction and increase involvement, you want a smoother UX. Jay