From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121088 invoked by alias); 28 Nov 2017 12:38:27 -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 121076 invoked by uid 89); 28 Nov 2017 12:38:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KB_WAM_FROM_NAME_SINGLEWORD,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.2 spammy=withdraw, complications, H*RU:sk:static., Hx-spam-relays-external:sk:static. X-HELO: mail-wm0-f43.google.com Received: from mail-wm0-f43.google.com (HELO mail-wm0-f43.google.com) (74.125.82.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 28 Nov 2017 12:38:21 +0000 Received: by mail-wm0-f43.google.com with SMTP id b189so1562000wmd.0 for ; Tue, 28 Nov 2017 04:38:21 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=9dXJQUI+VPiBEID4sYBJf3b7pCmPAbwPYfiUtITp/ms=; b=IEh2GaDPMtaRNam8dQX5dI4fUlprMEmirBgzVYNykc129AXnCpEKsdIWLRVZMlAjbe KYbkD+DTxC8ioAvHFa6bK/Cln8p7xTc/8EcMu0pDuAKe8LBWQ0fi3XoTt4QeIw3HfAZu PPq6jF8G52P+bmmzw+oDPjrhnsLVcj+CzX1zCQuausB4geG4XqejpH4vwNX72l/PQcck VNBWULlf94vghpDd4ph63yIrqUgUGszNa5liSsYecJrlO1Fhm0LBdZOTick/Z8sN8Cnt MNvaK2XqaELj12v2f9oYGtKCjfSsyfGuuJM/5a1VEMwsyvjncTzARKdLG4KOe7g+OCii cudg== X-Gm-Message-State: AJaThX6WO+RXjOCZHUv1DNloLcVtwiCJCVZFrZHAcDoGLFQu8pQ55+fO 3RkH6xIi1odFvSMNZvjOyyVnAQ== X-Google-Smtp-Source: AGs4zMZNHovyFWoT3DKQd6vcfw2UCS6YEb1lmViVgT/qDLzDjus3u576hEtdYwF5LNUbsSLj0OUPyg== X-Received: by 10.28.166.216 with SMTP id p207mr20924090wme.147.1511872699073; Tue, 28 Nov 2017 04:38:19 -0800 (PST) Received: from E107787-LIN (static.42.136.251.148.clients.your-server.de. [148.251.136.42]) by smtp.gmail.com with ESMTPSA id q89sm20327359wrb.95.2017.11.28.04.38.18 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Tue, 28 Nov 2017 04:38:18 -0800 (PST) From: Yao Qi To: Joel Brobecker Cc: gdb-patches@sourceware.org Subject: Re: time to create the GDB 8.1.x branch? References: <20171120191510.clz2ywdyknuftzrh@adacore.com> <86h8tmsbrg.fsf@gmail.com> <20171127220628.xdgwwvsrmrylw3go@adacore.com> Date: Tue, 28 Nov 2017 12:38:00 -0000 In-Reply-To: <20171127220628.xdgwwvsrmrylw3go@adacore.com> (Joel Brobecker's message of "Mon, 27 Nov 2017 14:06:28 -0800") Message-ID: <861skir32h.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2017-11/txt/msg00719.txt.bz2 Joel Brobecker writes: > Considering that the new feature only seems to be activated when > the necessary hwcap flag is set, it seems fine for me to backport it. > The one concern I have, however, is that 5 weeks is a bit long for > us to wait. Typically, what I would expect is for us to cut the > branch, then take a two/three weeks for people to field-test and > stabilize, before we actually create the release. > Hi Joel, Looks I overestimated the period after branch cut and release. I thought it is about 4 ~ 5 weeks, so I thought 4 weeks from now on, kernel patches *may* be merged, and GDB is not released yet, so I can squeeze these gdb patches in to 8.1 release. If the period is only 2~3 weeks, I don't want to delay the release. On the other hand, it takes some time for distro to pick up the Linux kernel or backport these kernel patches, the gdb feature can't be enabled without kernel support, so it doesn't matter too much that this feature is in gdb 8.1 or 8.2. > I don't have a problem with delaying the release after the branch > get created, but 5 weeks takes us roughly to start of 2018. I would > add an extra week or two after your backport before we actually > release, just in case there are unexpected complications with > the patch. So, we're talking mid-January. > > Any objections to a release around that time? Understood. I withdraw this proposal, and let us target your original plan. --=20 Yao (=E9=BD=90=E5=B0=A7)