From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101002 invoked by alias); 21 Sep 2019 09:26:57 -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 100993 invoked by uid 89); 21 Sep 2019 09:26:57 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=well!, learnt, 16th, 2nd X-HELO: gate.crashing.org Received: from gate.crashing.org (HELO gate.crashing.org) (63.228.1.57) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 21 Sep 2019 09:26:56 +0000 Received: from gate.crashing.org (localhost.localdomain [127.0.0.1]) by gate.crashing.org (8.14.1/8.14.1) with ESMTP id x8L9QoJ0012095; Sat, 21 Sep 2019 04:26:50 -0500 Received: (from segher@localhost) by gate.crashing.org (8.14.1/8.14.1/Submit) id x8L9QmrL012094; Sat, 21 Sep 2019 04:26:48 -0500 Date: Sat, 21 Sep 2019 09:26:00 -0000 From: Segher Boessenkool To: "Richard Earnshaw (lists)" Cc: gcc@gcc.gnu.org Subject: Re: Proposal for the transition timetable for the move to GIT Message-ID: <20190921092647.GW9749@gate.crashing.org> References: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1685e719-738f-dd4e-c39c-c08e495b202e@arm.com> User-Agent: Mutt/1.4.2.3i X-IsSubscribed: yes X-SW-Source: 2019-09/txt/msg00173.txt.bz2 On Tue, Sep 17, 2019 at 01:02:20PM +0100, Richard Earnshaw (lists) wrote: > At the Cauldron this weekend the overwhelming view for the move to GIT > soon was finally expressed. [ cutting and pasting a bit ] > There should be NO CHANGE to the other processes and policies that we > have, eg patch reviews, ChangeLog policies etc at this time. Adding > requirements for this will just slow down the transition by > over-complicating things. And I would add or generalise, NO SCOPE CREEP. We need to get this done now (or months or years ago). And that includes: > - tweaked committer history (email ids etc - nice to have) > - fixes for accidental trunk/branch deletions/restores (preferred) > - correctness around branch points (nice to have) Whatever of that is already done is fine of course, but we should not let any of this delay us a second further. > 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. And from then until the end of stage 4, everyone should learn how to use git, get used to the new workflow (people's *local* workflow; the global workflow does not change), etc. We should help each other getting things done where needed -- it is stage 4, we want that to go smoothly as well! -- but ideally when GCC 11 opens up everyone has learnt how to use Git efficiently. Thank you for this timeline Richard, I support it wholeheartedly. - - - NO MORE SCOPE CREEP - - - Segher