Return-Path: X-Original-To: apmail-htrace-dev-archive@minotaur.apache.org Delivered-To: apmail-htrace-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C5FC10A27 for ; Sun, 7 Dec 2014 01:41:00 +0000 (UTC) Received: (qmail 62924 invoked by uid 500); 7 Dec 2014 01:41:00 -0000 Delivered-To: apmail-htrace-dev-archive@htrace.apache.org Received: (qmail 62882 invoked by uid 500); 7 Dec 2014 01:41:00 -0000 Mailing-List: contact dev-help@htrace.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@htrace.incubator.apache.org Delivered-To: mailing list dev@htrace.incubator.apache.org Received: (qmail 62870 invoked by uid 99); 7 Dec 2014 01:40:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Dec 2014 01:40:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of andrew.purtell@gmail.com designates 209.85.214.171 as permitted sender) Received: from [209.85.214.171] (HELO mail-ob0-f171.google.com) (209.85.214.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Dec 2014 01:40:33 +0000 Received: by mail-ob0-f171.google.com with SMTP id uz6so2229384obc.2 for ; Sat, 06 Dec 2014 17:38:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:mime-version:subject :message-id:date:references:in-reply-to:to; bh=nvZJpNIbpTaT5raXTqUi7ByHXEkcXHG0m7unpnUehz8=; b=OLl1x+gRCk6KFD24Mq+uwgt4JN5ZyZcS3QY5gskE6Tq5giQKDbntMXHa8rlagbuW/X 4fJ70s8RhMnic5Kr/WSph7P3p0Vpor73/NeYzjA9ZxvFiMnCfezcMVFLyzHtdpZkOf3P mNjOVqlD2gBUb5kXK8Zyr8ImQRdweefE+GCLSq13lFGle1Gc3yjCsH7kanJhUFc+3/8Z IL3dnN+Og+WMsZJCh3/vOasDSqnO471IID7HE2sHGzfGZNHqud2guoq5MuKuTKSs7CEs QSaQtBKOnWiFGsaSlh47p860fF5mSdt0XAPM37jzDh8uajT1+Ebc1jjjYHu0zqPEeqqq rMXQ== X-Received: by 10.60.124.69 with SMTP id mg5mr3408910oeb.73.1417916297481; Sat, 06 Dec 2014 17:38:17 -0800 (PST) Received: from [192.168.1.106] (107-132-40-197.lightspeed.frsnca.sbcglobal.net. [107.132.40.197]) by mx.google.com with ESMTPSA id u23sm16175655oie.1.2014.12.06.17.38.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 06 Dec 2014 17:38:15 -0800 (PST) From: Andrew Purtell Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: What version should be the first apache htrace be? 4.0.0 or 1.0.0? Message-Id: <26D0B901-12DA-4D83-9BB5-85CA7FF2B82B@gmail.com> Date: Sat, 6 Dec 2014 17:38:14 -0800 References: In-Reply-To: To: "dev@htrace.incubator.apache.org" X-Mailer: iPhone Mail (12B436) X-Virus-Checked: Checked by ClamAV on apache.org What we did for Phoenix is make an initial ASF release that was the granted c= ode with a package name search-and-replace and minor version increment. This= let us focus on all the Apache packaging and release concerns like NOTICE f= ile wording, RAT compliance, etc. and provided an opportunity for existing u= sers to migrate to an ASF artifact at low risk - just package renames. Then w= e made a major version increment and put in some significant new features fo= r that next release.=20 > On Dec 5, 2014, at 9:36 PM, Nick Dimiduk wrote: >=20 > I think going backwards to 1.0 would be confusing for any existing users. > Maybe make the -incubating releases pickup 3.1.x with the intention of the= > first graduated release being 4.0.0. Could be seen as artificially > inflating the version numbers, but I don't think that matters too much. I > assume (prefer) we'll follow the guidelines of semantic versioning. >=20 > -n >=20 >> On Friday, December 5, 2014, Colin McCabe wrote:= >>=20 >> I looked at >> http://incubator.apache.org/guides/releasemanagement.html#best-practice-v= ersioning >> and it doesn't say whether we need to start at 1. Hmm. >>=20 >> I think either way could work. There is stuff from org.htrace up on >> Maven central, but since we're moving to org.apache.htrace, we won't >> conflict if we choose to go back to 1.0.0. I don't really have any >> preference between 1.0.0 or 4.0.0. >>=20 >> best, >> Colin >>=20 >> On Fri, Dec 5, 2014 at 7:47 PM, Stack > >> wrote: >>> org.htrace was at 3.0.4 >>>=20 >>> The next release could be 4.0.0. >>>=20 >>> Or we could roll back and make it 1.0.0? >>>=20 >>> Any opinions out there? >>>=20 >>> Thanks, >>> St.Ack >>=20