From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12297 invoked by alias); 1 Apr 2008 21:13:19 -0000 Received: (qmail 12289 invoked by uid 22791); 1 Apr 2008 21:13:19 -0000 X-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_50,J_CHICKENPOX_55,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 01 Apr 2008 21:13:01 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id m31LD0dv006302 for ; Tue, 1 Apr 2008 17:13:00 -0400 Received: from pobox-3.corp.redhat.com (pobox-3.corp.redhat.com [10.11.255.67]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m31LCxSN030188; Tue, 1 Apr 2008 17:12:59 -0400 Received: from toner.yyz.redhat.com (toner.yyz.redhat.com [10.15.16.55]) by pobox-3.corp.redhat.com (8.13.1/8.13.1) with ESMTP id m31LCwpT012433; Tue, 1 Apr 2008 17:12:59 -0400 Message-ID: <47F2A55A.70205@redhat.com> Date: Tue, 01 Apr 2008 21:13:00 -0000 From: Sami Wagiaalla User-Agent: Thunderbird 2.0.0.12 (X11/20080226) MIME-Version: 1.0 To: Phil Muldoon CC: Andrew Cagney , frysk Subject: Re: meeting 2008-03-19 - version numbers References: <47E12D0D.1020309@redhat.com> <47E13868.7060507@redhat.com> In-Reply-To: <47E13868.7060507@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.58 on 172.16.52.254 X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2008-q2/txt/msg00002.txt.bz2 >> b) move to regular (monthly?) patch-level releases; e.g., 0.8.1, >> 0.8.2, ... > I've no objections to this. But: > > - What release schedule? Weekly? Monthly? I propose: - monthly releases with news items. - We create a NEWS file that we dump every release. > > - How will we be smoke testing the results to ensure sanity (ie the last > patch pushed screwed some stuff up). Our test cases can catch a lot of > this? What is the release checklist? > We make sure all the tests pass, and add tests are user report problems. We can also push a package to updates testing test it for a week then move it. Although I personally prefer the smoke test it and get it out there ASAP approach. > - Because we are moving to a more formal release deadline, how do > development practices change, if at all? > I dont know. Depends on what is motivating this change and what options we have to solve it. > - What is our release matrix. Fedora 8 now, and Rawhide. But will it > then be F8, F9 and rawhide all in sync? Will the release be to rawhide > first, then a monthly push from rawhide to Fedora *? > We are a young project so we want to stay agile as much as possible. So I suggest we release to rawhide and the latest fedora. > - How can we detect regressions in stability and features > Tests, and users(frysk team ? :))