cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Braden Shepherdson <bra...@chromium.org>
Subject Re: tagging on plugman / cli
Date Tue, 03 Sep 2013 17:14:23 GMT
Ooh, I didn't know about that command. I agree that it's a good way to
go... except that the wonky version numbers of the tools (3.0.0-0.10.2)
might make that impossible. Or is that valid semver?


On Tue, Sep 3, 2013 at 1:10 PM, Brian LeRoux <b@brian.io> wrote:

> 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 <mmocny@chromium.org> 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 <agrieve@chromium.org>
> > 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
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message