Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BAD82107A7 for ; Tue, 3 Sep 2013 17:11:24 +0000 (UTC) Received: (qmail 39553 invoked by uid 500); 3 Sep 2013 17:11:24 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 39506 invoked by uid 500); 3 Sep 2013 17:11:24 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 39498 invoked by uid 99); 3 Sep 2013 17:11:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 17:11:24 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of brian.leroux@gmail.com designates 209.85.223.182 as permitted sender) Received: from [209.85.223.182] (HELO mail-ie0-f182.google.com) (209.85.223.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Sep 2013 17:11:17 +0000 Received: by mail-ie0-f182.google.com with SMTP id aq17so10838903iec.41 for ; Tue, 03 Sep 2013 10:10:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=1BRBLu5IieuKkgtpGlwOyni5XUTFugAcILH0N/aOCX8=; b=WAohpEK3f1M1BJzlpipRYVRHKkrnPOzWOi03SUWy7wT2vdNDwKNrHYpHgUsPTRDqrl RH89m5W5RNOBWCKB11RxwqlSPVKYuywnJ2ZKuvYAzfl/StZ317vTYxrKfKxyTahH43G9 YZK++tq5wmbXGr5FhKGEYQHOHOhdB/84Gn6i/UobUpPQV82AqJYBKL5uaRixSyXbFQVU ogSSPmqfkvPJXUS+EmiANCPaFVHSQJWmtls6Pcqv/vp8c90Cl1yj4+LKYv0W0qhsMaFO BaW1Abw1POC7MBaT/Dzuz3I1Vh9qROI1ppXhq496mBmFMX7HEu/K566/VmaxrvRxYmh5 ytWQ== MIME-Version: 1.0 X-Received: by 10.50.88.7 with SMTP id bc7mr16670742igb.37.1378228257032; Tue, 03 Sep 2013 10:10:57 -0700 (PDT) Sender: brian.leroux@gmail.com Received: by 10.50.114.132 with HTTP; Tue, 3 Sep 2013 10:10:56 -0700 (PDT) In-Reply-To: References: Date: Tue, 3 Sep 2013 10:10:56 -0700 X-Google-Sender-Auth: zbctVw3t3bvsFnMpmhB5ha2lh-0 Message-ID: Subject: Re: tagging on plugman / cli From: Brian LeRoux To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=089e01184168ae14e004e57dc588 X-Virus-Checked: Checked by ClamAV on apache.org --089e01184168ae14e004e57dc588 Content-Type: text/plain; charset=ISO-8859-1 we should encourage `npm version` as the method to ensure things stay in sync (run `npm help version` to see what I'm talking about) On Tue, Sep 3, 2013 at 10:00 AM, Michal Mocny wrote: > If I understand correct, these tags aren't going to be used by npm, just > make it easier for us to map npm releases to git hash's? > > Sounds fine, but hoping these stay well lined up over time. > > > On Tue, Sep 3, 2013 at 12:33 PM, Andrew Grieve > wrote: > > > Right now CLI & plugman don't have git tags associated with their npm > > releases. > > > > I'd like to be able to do a "git log latest..master" in order to > enumerate > > changes since the last release. > > > > So, I'd like to propose: > > #1 - Add a git tag for each npm release, where the tag name is the same > as > > the version > > #2 - Add a git tag called "latest", which points to the most recent > release > > > > I've added this already to > > https://wiki.apache.org/cordova/StepsForToolsRelease, but wanted > explicit > > buy-in here. #1 will result in a lot of tags being created over time > (which > > I think is fine). > > > > Andrew > > > --089e01184168ae14e004e57dc588--