cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Higgins <br...@bryanhiggins.net>
Subject Re: [DISCUSS] Plugin master branches
Date Tue, 22 Apr 2014 14:23:34 GMT
+1

I think the registry has been around for long enough that the vast majority
of users won't be installing directly from git.


On Tue, Apr 22, 2014 at 9:44 AM, Ian Clelland <iclelland@chromium.org>wrote:

> I totally agree that we should do this.
>
> I think that once the current plugin release is complete, I can set up the
> branches so that the master branch is for development, and we can go from
> there.
>
> Is it a requirement that plugins be tagged in git for npm to function? I
> thought that the plugins were uploaded, zipped, to our couch server, for
> each release, and that there was no further communication with the git
> repository? It shouldn't be a problem to go back and make sure they're
> properly tagged, but I'm just wondering if it's still a necessity.
>
> Ian
>
> On Mon, Apr 21, 2014 at 9:27 PM, Jesse <purplecabbage@gmail.com> wrote:
>
> > I am seeing more and more pull requests that aren't easy merges because
> > people are starting their work from the master branch, and not dev.
> >
> > We discussed *a long time ago* that at some point, we would consider
> master
> > to be the bleeding edge of each plugin, and we could then get rid of the
> > dev branches.  The requirements to make this possible included, using a
> > branch/tag for every npm release of the plugin, and making sure that
> plugin
> > dependencies were correctly mapped.
> >
> > Has anyone given this any more thought, and do we have any idea when we
> > will make the switch?
> >
> > Cheers,
> >   Jesse
> >
> >
> > @purplecabbage
> > risingj.com
> >
>

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