From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118755 invoked by alias); 25 Oct 2019 14:02:55 -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 118746 invoked by uid 89); 25 Oct 2019 14:02:55 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-6.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=trial, evidence, meet, our X-HELO: foss.arm.com Received: from foss.arm.com (HELO foss.arm.com) (217.140.110.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 25 Oct 2019 14:02:54 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 851A828; Fri, 25 Oct 2019 07:02:51 -0700 (PDT) Received: from e120077-lin.cambridge.arm.com (e120077-lin.cambridge.arm.com [10.2.206.225]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 9F83F3F71A; Fri, 25 Oct 2019 07:02:50 -0700 (PDT) Subject: Re: Proposal for the transition timetable for the move to GIT To: Paul Koning Cc: gcc@gcc.gnu.org, Maxim Kuvyrkov , "Eric S. Raymond" References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> <0989403D-2837-41C3-B7BF-CED32AEBD82D@comcast.net> From: "Richard Earnshaw (lists)" Message-ID: Date: Fri, 25 Oct 2019 14:02:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <0989403D-2837-41C3-B7BF-CED32AEBD82D@comcast.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2019-10/txt/msg00157.txt.bz2 On 19/09/2019 18:04, Paul Koning wrote: > > >> On Sep 17, 2019, at 8:02 AM, Richard Earnshaw (lists) wrote: >> >> ... >> So in summary my proposed timetable would be: >> >> Monday 16th December 2019 - cut off date for picking which git conversion to use >> >> Tuesday 31st December 2019 - SVN repo becomes read-only at end of stage 3. >> >> Thursday 2nd January 2020 - (ie read-only + 2 days) new git repo comes on line for live commits. > > That sounds ok but it feels incomplete; there are additional steps and dates needed leading up to the 16th December decision point. > > I would suggest: 1 December 2019: final version of each proposed conversion tool is available, trial conversion repository of the full GCC SVN repository is posted for public examination. > > That allows 2 weeks for the different tools and their output to get the scrutiny needed for the picking decision to be made. 2 weeks may be more than needed (or possibly, less), but in any case I think this piece needs to be called out. I don't think I want to start setting more hard deadlines. I'll simply say, the decision will be made on that date, based on the evidence we have. It's up to the proponents of the various conversion alternatives to be able to demonstrate before that time that their conversion meets the required criteria. I'm not interested in reviewing the tools used, per se. I am interested in ensuring that the conversions produced by them meet our requirements. Of course, if a sample conversion is only delivered the day before the deadline, we may have to decide that that doesn't leave us enough time to review it. But that might depend on what accompanying evidence is supplied along with such a conversion. R.