From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Release process (was Re: Move to a cadence release model?) Date: Wed, 11 Nov 2015 08:39:10 -0800 Message-ID: References: <8337wdn6uu.fsf@gnu.org> <86611975jo.fsf_-_@stephe-leake.org> <838u65kxly.fsf@gnu.org> <86mvuk4xxd.fsf@stephe-leake.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1447260657 14060 80.91.229.3 (11 Nov 2015 16:50:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 11 Nov 2015 16:50:57 +0000 (UTC) Cc: Eli Zaretskii , john@yates-sheets.org, emacs-devel@gnu.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 11 17:50:51 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZwYbf-0000K3-0m for ged-emacs-devel@m.gmane.org; Wed, 11 Nov 2015 17:50:47 +0100 Original-Received: from localhost ([::1]:41721 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwYbe-0007Nb-FW for ged-emacs-devel@m.gmane.org; Wed, 11 Nov 2015 11:50:46 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42290) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwYbG-0007Kd-KQ for emacs-devel@gnu.org; Wed, 11 Nov 2015 11:50:38 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwYay-0000oV-0W for emacs-devel@gnu.org; Wed, 11 Nov 2015 11:50:22 -0500 Original-Received: from mail-pa0-x230.google.com ([2607:f8b0:400e:c03::230]:36564) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwYab-0000fD-22; Wed, 11 Nov 2015 11:49:41 -0500 Original-Received: by pacdm15 with SMTP id dm15so35430945pac.3; Wed, 11 Nov 2015 08:49:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:mail-followup-to:mime-version:content-type; bh=u3qmJXZaLO6+fazJgeBoZdp2CGHJytFNj0nK/15YMO4=; b=ORU0n971WZCwHZXrhOm2K8jD9LNEE+V6NdAdy1mQmgF32ABPbyTkVGnvANBHjEqYew 9pthaqISg8E0HhrcwEeW13qcNKIyo7RAH0DdLcBD2kYVDt5EH8c8wlhywMsMI00CTbWL JAHtJM+VgAQMXR/xcjVdPFW5jY9WuuHLy9qXNtVDQNL7VIDOY35GxqSBpIMjkeNRqVoD sO6xlWQAynihlZ/gKeZwSv0jS3AOrxW/5JuT1+UvZ9KVwIrmZDje5UW0c/oMwsYUAzvo +8T8zhEb/FWus5JYCeIE+4ROxEjGQ+Ktkfrq6CSUJOsVtv/jIJpjGW3LaBLYYrtP+1FF iYsA== X-Received: by 10.66.234.133 with SMTP id ue5mr15668135pac.56.1447260580580; Wed, 11 Nov 2015 08:49:40 -0800 (PST) Original-Received: from Vulcan.attlocal.net (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id j12sm10230926pbq.55.2015.11.11.08.49.39 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 11 Nov 2015 08:49:39 -0800 (PST) X-Google-Original-From: "John Wiegley" Original-Received: by Vulcan.attlocal.net (Postfix, from userid 501) id 45A7A10546017; Wed, 11 Nov 2015 08:49:39 -0800 (PST) In-Reply-To: <86mvuk4xxd.fsf@stephe-leake.org> (Stephen Leake's message of "Wed, 11 Nov 2015 04:45:18 -0600") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: Stephen Leake , Eli Zaretskii , emacs-devel@gnu.org, john@yates-sheets.org X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::230 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194089 Archived-At: >>>>> Stephen Leake writes: > I don't have statistics on how well the feature-freeze model works in > getting release-critical bugs fixed. Have we had other release models in the > past? did they work any better? I'm not entirely sure how our freeze model worked in the past, but here's what I intend: The 25.1 release branch isn't ready until all its critical bugs are resolved. This means we'll need a 25.1 tag, and we'll need to go through all current high severity bugs to determine which should receive that tag. Then the clock starts, until either we have closed the last one, or removed all such tags. The motivation for working on a release branch has several aspects: (1) 25.1 isn't released until it's ready, so if you have work you're proud that you want to set free, help! (2) My focus will be on 25.1, and not on future features, so until we have 25.1 out the door, our discussions may not be as fun. (3) It will give all of us a chance to hone our bugtracker skills, and make it an easier process so future releases go more smoothly. I'm open to making changes to reduce developer inertia here, and you can be part of that by telling me about your experiences. John