Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of agrieve@google.com designates
 209.85.160.49 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
From: Andrew Grieve <agrieve@chromium.org>
Date: Tue, 3 Sep 2013 12:33:51 -0400
Message-ID: 
 <CABiQX1WccbhTVqHsOt=0zg3jSqBEW3SM9V4wObA-jKAseFgH9Q@mail.gmail.com>
Subject: tagging on plugman / cli
To: dev <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=e89a8ffbabed31bdcd04e57d42f4

--e89a8ffbabed31bdcd04e57d42f4
Content-Type: text/plain; charset=ISO-8859-1

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

--e89a8ffbabed31bdcd04e57d42f4--