From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27222 invoked by alias); 16 Dec 2019 16:39:18 -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 27201 invoked by uid 89); 16 Dec 2019 16:39:17 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,SPF_PASS autolearn=ham version=3.3.1 spammy=managers, HX-Languages-Length:1368, timing X-HELO: us-smtp-delivery-1.mimecast.com Received: from us-smtp-1.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (207.211.31.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 16 Dec 2019 16:39:15 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1576514353; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=erqtJhZN7k6e2LAzGCXnT3W+B5YUBtOqlvtwX8K6+OM=; b=dgzKDE4oEbgjxnaDuZUxWJlhC9275ONelRirjEsziuEjwePGS91sYbh/tJAFt4y9UrDHmP HTlgZTLXj+EGiVPr0bTHHW0MFP5SZUxT7RPmIdg/QoVpD7WWRc5DpwoUBkB8q/Ti5iF/hw 0k1Si5YlToDg4WHKY9QaGdjo1B1U3sM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-361-Npl7EHOCNO6vijub56o_zg-1; Mon, 16 Dec 2019 11:39:09 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 12850107B791; Mon, 16 Dec 2019 16:39:08 +0000 (UTC) Received: from ovpn-112-27.phx2.redhat.com (ovpn-112-27.phx2.redhat.com [10.3.112.27]) by smtp.corp.redhat.com (Postfix) with ESMTP id 65D721001B00; Mon, 16 Dec 2019 16:39:07 +0000 (UTC) Message-ID: <63bb91a7377e4410d7ca475cb38a7f3f2297280b.camel@redhat.com> Subject: Re: Proposal for the transition timetable for the move to GIT From: Jeff Law Reply-To: law@redhat.com To: Joseph Myers , Mark Wielaard Cc: Maxim Kuvyrkov , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org, esr@thyrsus.com Date: Mon, 16 Dec 2019 16:39:00 -0000 In-Reply-To: References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <9E009921-96EA-44A2-A06A-232711227E69@linaro.org> User-Agent: Evolution 3.34.2 (3.34.2-1.fc31) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-12/txt/msg00242.txt.bz2 On Mon, 2019-12-16 at 13:53 +0000, Joseph Myers wrote: > > > > However, we should also note that stage 3 is intended to last two months, > > > ending with the move to git > > > > > > ;, and given that it > > > didn't start at the start of November as anticipated in the originally > > > proposed timetable, that implies corresponding updates to all the dates. > > > By now, enough people are away until the new year that now isn't a good > > > time for deciding things anyway. > > > > 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. > > It was also that doing it at the end of stage 3 would mean the least > disruption to development for stage 3. That suggests converting over the > 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. Jeff