Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 43296 invoked from network); 29 Jun 2009 13:30:48 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Jun 2009 13:30:48 -0000 Received: (qmail 17349 invoked by uid 500); 29 Jun 2009 13:30:58 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 17281 invoked by uid 500); 29 Jun 2009 13:30:58 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Delivered-To: moderator for core-dev@hadoop.apache.org Received: (qmail 10502 invoked by uid 99); 29 Jun 2009 13:26:41 -0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:content-type:content-transfer-encoding; b=GGRYJSgYIcItpgIEHZb0w1+wQz1nOEXTfYgTS2rJ0crhT6cEv9A5e+hiDbU10XOz Message-ID: <4A48C0D7.5010204@yahoo-inc.com> Date: Mon, 29 Jun 2009 18:55:43 +0530 From: Vinod KV User-Agent: Thunderbird 2.0.0.21 (X11/20090409) MIME-Version: 1.0 To: core-dev@hadoop.apache.org Subject: Re: Apache git mirrors, post project split References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Steve Loughran wrote: > Chris Douglas wrote: > > The new git repositories for HDFS and Map/Reduce, > > git://git.apache.org/hadoop-{mapreduce,hdfs}.git are up. > > > > There are two open issues: > > (1) What to do with the defunct git mirror that points to core > > (2) What to call the common mirror > > > > For (1), I'd advocate simply deleting it. There doesn't seem to be a > > compelling case for maintaining an archive of a mirror next to its > > active replacements. > > How about pre-announce a planned deletion some months ahead, give people > time to migrate off > +1, for leaving it alone for some time as Steve says. > > For (2), the git mirror is currently being built as hadoop-common.git. > > Since it will contain the pre-0.21 tagged releases/branches and > > developers pulling from the old mirror will error out either way, I'd > > lean toward calling it hadoop.git, but am mostly ambivalent on this. > > > > The ticket for this is INFRA-2108. -C I think hadoop-common.git is better - pre-21 hadoop-common contains everything, post that, it only has common stuff. But like you, have no strong opinion on this. +Vinod