From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 86041 invoked by alias); 20 Jul 2016 17:24:23 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 85260 invoked by uid 89); 20 Jul 2016 17:24:22 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=shoot, aug, Aug, deemed X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Wed, 20 Jul 2016 17:24:21 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 780BE117024 for ; Wed, 20 Jul 2016 13:24:19 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9VYGZeTmq42o for ; Wed, 20 Jul 2016 13:24:19 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 48C1C11701F for ; Wed, 20 Jul 2016 13:24:19 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id C107E428F7; Wed, 20 Jul 2016 10:24:17 -0700 (PDT) Date: Wed, 20 Jul 2016 17:24:00 -0000 From: Joel Brobecker To: gdb-patches@sourceware.org Subject: RFC: gdb-7.12 timeframe? Message-ID: <20160720172417.GA3601@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2016-07/txt/msg00225.txt.bz2 Hello, It's been almost 6 months since we started our previous release cycle, so now is a good time to consider whether or not we feel we have enough goodies to start a new process. We have two questions to answer: 1. When to start the process (ie stabilize master and create the release branch); 2. What timeframe to shoot for in terms of the 7.12 release. The part that worries me is that we're about to enter the month of Aug, which is traditionally a very slow month due to summer holidays. What I would like to propose is we try to create the branch soon. This means we make a call for blocking issues before the branch is created, and create the branch, say, one week from now. Issue a first pre-release then. Meanwhile, we can try fixing all reported issues that were found and deemed blocking for the release. To avoid having some issues being reported too late, I propose we wait for September to make our the 7.12 release. If necessary, we can make a second pre-release early september. Thoughts? -- Joel