X-Original-To: pgsql-hackers-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 198C39FB4C7 for ; Sat, 2 Sep 2006 07:55:43 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 04403-03 for ; Sat, 2 Sep 2006 07:55:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from fetter.org (start.fetter.org [66.92.188.65]) by postgresql.org (Postfix) with ESMTP id 7B8DF9FB4A8 for ; Sat, 2 Sep 2006 07:55:31 -0300 (ADT) Received: by fetter.org (Postfix, from userid 500) id EDBBBF3D3FB; Sat, 2 Sep 2006 03:55:28 -0700 (PDT) Date: Sat, 2 Sep 2006 03:55:28 -0700 From: David Fetter To: "Jonah H. Harris" Cc: Bruce Momjian , Peter Eisentraut , pgsql-hackers@postgresql.org, Tom Lane , josh@agliodbs.com Subject: Re: Getting a move on for 8.2 beta Message-ID: <20060902105528.GA27879@fetter.org> References: <200609020209.36483.peter_e@gmx.net> <200609020036.k820aWr26205@momjian.us> <36e682920609011913k5016d790raf49abd37dad5e07@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36e682920609011913k5016d790raf49abd37dad5e07@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.153 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200609/115 X-Sequence-Number: 89644 On Fri, Sep 01, 2006 at 10:13:07PM -0400, Jonah H. Harris wrote: > On 9/1/06, Bruce Momjian wrote: > >I pummelled Jonah over the recursive query patch. > > He did. Trust me on this... think I still have some bruises too :) That wasn't productive. Getting it out in public that your available time didn't match the size of the project in, say, February or even April, would have been. > >Neither effort was very fruitful, but tracking wasn't what made > >them fail. I am not saying tracking is wrong, but rather tracking > >would not have helped make these things happen faster. > > This is correct. I just had too much stuff to do and there wasn't > enough time to get the hierarchical query patch worthy of someone > spending their time on a review. I know it's hard to judge from the inside, which is why this process needs more public visibility, early and often, to the rest of the community. It does nobody any good to have Bruce bawl you out repeatedly in private, and then spring it on the rest of us in June that you weren't even close. > IMHO, tracking occasionally is alright. However, as a developer, > being "pummelled" does sometimes get irritating; even to the point > that I will sometimes discontinue working on something because it's > too much of a hassle for me to spend my free-time on. That's an excellent outcome for the project, by the way. When somebody is feeling "pummeled," it's frequently a signal that they really don't have the time they thought they did, and the sooner and more widely such a situation is known, the better. > Though, this was not the case for hierarchical queries at all; that > really was due to a lack of time. > > There's got to be a "happy medium" in which we can keep our status > updated without it becoming an irritation. Has anyone looked at > something like dotProject? It may be something we could use for > development. Of course, there's lots of other tools... but it would > be nice if we had a central location for each task's status so that > we don't have to resort to searching email and/or archives. ...and we're back to the infamous tarbaby of bug/issue trackers. It's time we took that head-on instead of dancing around it. As expressed many times earlier, such a system must be accessible, both for read and write, by email. What other things must it do? Should it do? Must it avoid? Cheers, D -- David Fetter http://fetter.org/ phone: +1 415 235 3778 AIM: dfetter666 Skype: davidfetter Remember to vote!