From owner-freebsd-current@FreeBSD.ORG Sun Sep 27 02:33:40 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9507E106566C for ; Sun, 27 Sep 2009 02:33:40 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 27E758FC16 for ; Sun, 27 Sep 2009 02:33:39 +0000 (UTC) Received: from [10.29.62.2] (port=62755 helo=Aris-MacBook-Pro.local) by fish.ish.com.au with esmtpa (Exim 4.69) (envelope-from ) id 1MrjaZ-00064Y-30; Sun, 27 Sep 2009 12:34:16 +1000 Message-ID: <4ABECEFD.5020001@ish.com.au> Date: Sun, 27 Sep 2009 12:33:33 +1000 From: Aristedes Maniatis User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.4pre) Gecko/20090915 Shredder/3.0b4pre MIME-Version: 1.0 To: Robert Watson References: <20090921112657.GW95398@hoeg.nl> <19e9a5dc0909211728m159c1b50id00dec2b3f8110b0@mail.gmail.com> <20090922101329.K39832@ury.york.ac.uk> <200909221231.27713.gnemmi@gmail.com> <20090922174713.B39832@ury.york.ac.uk> <19e9a5dc0909221042l4f5a3e13p27776ee8bbc9713e@mail.gmail.com> <20090922225905.GC21416@lonesome.com> <4ABD68FA.5010103@ish.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark Linimon , Gonzalo Nemmi , current@freebsd.org Subject: Re: Various problems seen in RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Sep 2009 02:33:40 -0000 On 27/09/09 9:52 AM, Robert Watson wrote: > Unfortunately, I fell behind due to running the developer summit and > EuroBSDCon, but really that's a symptom of an underlying problem: I was > (and > am) manually maintaining the wiki list based on re@ e-mail correspondence. > > That is fundamentally the wrong approach--we should be using the > bug-tracking system to manage pending requests and known issues. In > particular, I'd like each merge request and in-progress issue to be > captured by a bug entry, and referenced during commits and merges. This > would allow 99% of the information on the wiki page to be mechanically > generated, and avoid the "missed stuff" problem. We'd also have to get > better at saying "it's a real bug but we can't > fix it for this release" explicitly, of course. > > There's not an opportunity to fix that for 8.0, but my recommendation > has been that we at least use gnats, if not some more capable, > issue-tracking system to handle pending changes and merge requests, with > approvals to commit to > branches linked back to the request so re@ can track what's going on. Absolutely! And my mention of your wiki page was certainly not a criticism of your efforts with the wiki page. A valiant effort I think (and much more useful than no information at all), but as you say, fundamentally doomed. Far too much work to maintain over more than a very short period. I sent you/Mark an email in February about this topic and my offer to help because I think this is one area where FreeBSD communication channels could be significantly improved without creating more work (after the short term effort of change of course). Any one of about a dozen sophisticated bug trackers would be capable of integrating svn linking, bug tracking, feature requests, feature voting, milestone management, developer task assignment, release management, release notes, and even have a workflow component that could integrate with the ports lifecycle (port owners without commit rights). Regards Ari Maniatis -- --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A