From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 09:57:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CE9F106564A for ; Mon, 8 Dec 2008 09:57:42 +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 CB2E38FC16 for ; Mon, 8 Dec 2008 09:57:41 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from ip-132.ish.com.au ([203.29.62.132]:56360) by fish.ish.com.au with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1L9dNe-0001GK-2W for freebsd-stable@freebsd.org; Mon, 08 Dec 2008 21:30:22 +1100 Message-Id: From: Aristedes Maniatis To: freebsd-stable Stable Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 8 Dec 2008 20:57:37 +1100 X-Mailer: Apple Mail (2.929.2) Subject: visibility of release process X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 09:57:42 -0000 I've resisted sending this email for a while since I really don't want to start a bikeshed nor a flame. However there comes a time to express my thoughts over the lack of visibility of the release process for FreeBSD 7.1. Here are the resources I am aware of: * release timeline [1]. This page makes no mention of beta 2 which is now some weeks old, so I assume the page is not actively used as a communication tool for the status of the release. * this list [2]. Although betas are announced here, there is no information about what is happening next. * subversion. Without checking out the whole repository, it is a little hard to use this as a news source and emails to the commit list still look more like cvs than svn so it is a bit hard to see which branch commits are going to. [3] * the bug tracker. Let's just say that FreeBSD's bug tracker is fairly primitive and 'target release' is not an option. I'd like to make several suggestions which could improve the transparency of the release process: 1. Short term fix: re could make a progress announcement on the appropriate lists every 14 days during the release process. Just a short summary of URLs pointing to the bug tracker. 2. Some web based friendly end-user visibility on the commit process, per branch. People can see what is going in and being fixed, but not what is left outstanding. Fisheye is an option because it costs nothing except the small load on the svn server. 3. Improvements to the bug tracker. Personally I'd love to see something like Jira used [4] with all the sophistication of workflow, release notes, voting for bugs, etc, etc. I'm happy to help with 2 and/or 3 in terms of contribution of my time and experience. Cheers Ari Maniatis [1] http://www.freebsd.org/releases/7.1R/schedule.html [2] That is FreeBSD-stable [3] I've also made an attempt to have Atlassian use Fisheye to produce an friendly overview of the repository, however I need to get permission from FreeBSD for this to happen before Atlassian will go ahead and index the whole svn repository. I've been unable to get anyone to respond to my requests in that regard. The result might look a bit like this: http://fisheye6.atlassian.com/ [4] Disclaimer: I am an Atlassian partner and like their products, but stand to gain nothing by the decision FreeBSD core make, I just think it is the best product for FreeBSD's requirements and it works well over at Apache. --------------------------> 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