From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 74483 invoked by alias); 21 Jul 2016 10:32:56 -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 74400 invoked by uid 89); 21 Jul 2016 10:32:56 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:1537, Meanwhile, month, travel X-HELO: mail-oi0-f43.google.com Received: from mail-oi0-f43.google.com (HELO mail-oi0-f43.google.com) (209.85.218.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 21 Jul 2016 10:32:42 +0000 Received: by mail-oi0-f43.google.com with SMTP id l72so111339331oig.2 for ; Thu, 21 Jul 2016 03:32:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=dgNbtSajjTcB96/YF/P7cE42U1DPUcIhNuJaZLJc9wE=; b=cIVLe2NUGj/tZyP6wg0Ed2/GE4Oz7Rq3dNI78aNQz6+mHkhueFE9nq0q2EPr7Le4FY iFsAHFzOnj9w4Nrq1WlLNU8DJnoW5+GzTcw42eXGlOjAdw9MhXuPExSBHLmcLNOdqoUZ fLeW8hKK94y4/dSdlMgs+ZHtNGeBHQSaCCpZ/1AbrN+PGRmCXONFT0+OpufKMRvmDpAZ 9BP0OHVaAneeWibM5VGL2q0mkPgk37YmbJv5Msdhw3hoW4ksRf/W88LJ3FXn9XwGPqCQ 3v1tyBBGKYyk6JdPkxVZme97zqYvNTHa8uuE9Cl3xtKqTSBs1RongRa4nc/ojwt9YMOF +hgA== X-Gm-Message-State: ALyK8tKaO0vt6fvWYh/yFxGE+hrHimjQdtztz4dbu+HnZ6T8TK5NguWa52kO5BQ6O7qmqNC/4BP85AvrdMYzLg== X-Received: by 10.157.33.125 with SMTP id l58mr30420369otd.32.1469097160795; Thu, 21 Jul 2016 03:32:40 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.105.138 with HTTP; Thu, 21 Jul 2016 03:32:40 -0700 (PDT) In-Reply-To: <20160720172417.GA3601@adacore.com> References: <20160720172417.GA3601@adacore.com> From: Yao Qi Date: Thu, 21 Jul 2016 10:32:00 -0000 Message-ID: Subject: Re: RFC: gdb-7.12 timeframe? To: Joel Brobecker Cc: "gdb-patches@sourceware.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2016-07/txt/msg00239.txt.bz2 On Wed, Jul 20, 2016 at 6:24 PM, Joel Brobecker wro= te: > 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. We need collect issues first, and decide whether one week is enough to stabilize the master and create branch then. I didn't follow the regression tests in buildbot, but I'll take a look. Do we have a wiki page to track all these issues for release? > > 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. I have a travel at the end of the Sep, but I think 7.12 is already released then. The time is good to me. --=20 Yao (=E9=BD=90=E5=B0=A7)