From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101624 invoked by alias); 16 Dec 2019 17:57:34 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 101615 invoked by uid 89); 16 Dec 2019 17:57:33 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=mid, H*f:sk:63bb91a, H*i:sk:63bb91a X-HELO: mail-wm1-f42.google.com Received: from mail-wm1-f42.google.com (HELO mail-wm1-f42.google.com) (209.85.128.42) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 17:57:32 +0000 Received: by mail-wm1-f42.google.com with SMTP id t14so243752wmi.5 for ; Mon, 16 Dec 2019 09:57:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:cc:from:message-id; bh=S4wpmD3p6MmZEDB7t2cp8rPSXm1M1+64eckoaHTlIw8=; b=lgXCbrPBh5l+XJrUG0+ncrnHKwYQju1uE6A4bOA+bhYbDKQx3q7QtU0A2UAsOs4cUN dEQZWAyllCp/2iJxehFm3GBy1soBou92SOt8qlUldRHsfMX/kQ3PQQJLkNzfeCdWLS84 3kN3n/8MBmzW3F5wPrxHUzIzhx8a4RpwTkolZuKCKelJHTjH3Z5971c3F6am31HqsEmx LxMtSROf/hQ556q8Mzlz6Qqh4jUNQOInYA50J3zQ9Z4vXy7XLLsJGSM/mMqNpMJr8Eqc MZkZLjgmxXUV9K60pPJIayeWAoXsFnUkKuH41xNK6SF+gk2kyw5nskFAF/hR+wF4ZMwC pQKA== Return-Path: Received: from [192.168.178.32] (x5f730d97.dyn.telefonica.de. [95.115.13.151]) by smtp.gmail.com with ESMTPSA id c195sm130438wmd.45.2019.12.16.09.57.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Dec 2019 09:57:29 -0800 (PST) Date: Mon, 16 Dec 2019 17:57:00 -0000 User-Agent: K-9 Mail for Android In-Reply-To: <63bb91a7377e4410d7ca475cb38a7f3f2297280b.camel@redhat.com> References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> <63bb91a7377e4410d7ca475cb38a7f3f2297280b.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Proposal for the transition timetable for the move to GIT To: law@redhat.com,Jeff Law ,Joseph Myers ,Mark Wielaard CC: Maxim Kuvyrkov ,"Richard Earnshaw (lists)" ,gcc@gcc.gnu.org,esr@thyrsus.com From: Richard Biener Message-ID: <464C7391-AF35-4966-9341-E6A41FD1944B@gmail.com> X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00249.txt.bz2 On December 16, 2019 5:39:06 PM GMT+01:00, Jeff Law wrote: >On Mon, 2019-12-16 at 13:53 +0000, Joseph Myers wrote: >>=20 >> > > However, we should also note that stage 3 is intended to last two >months,=20 >> > > ending with the move to git=20 >> > > =20 >> > > ;, and given >that it=20 >> > > didn't start at the start of November as anticipated in the >originally=20 >> > > proposed timetable, that implies corresponding updates to all the >dates.=20=20 >> > > By now, enough people are away until the new year that now isn't >a good=20 >> > > time for deciding things anyway. >> >=20 >> > The idea was to do it while most people were away to have the least >> > impact. The timeline https://gcc.gnu.org/wiki/GitConversion does >say we >> > can slip for logistical reasons the read-only date (2019/12/31) by >a >> > few days. >>=20 >> It was also that doing it at the end of stage 3 would mean the least=20 >> disruption to development for stage 3. That suggests converting over >the=20 >> weekend of 18/19 January, given the current stage 3 timings. >My recollection was the timing was meant to land roughly at the stage3- >>stage4 transition. So the question is whether or not we're on target >with that. Based on the regression counts, probably not at this point, >but I'll let the release managers chime in on that point. > Fortunately that's a pure timing thing and I'd expect stage3 to end mid Jan= uary, possibly scrapping off a week to help the git conversion.=20 Richard.=20 >Jeff