@maxw: done!
On Tue, Sep 17, 2013 at 1:55 PM, Shazron <[email protected]> wrote: > @Anis yeah this could be a documentation issue. We will have to update the > 3.0.0 specific docs. > > > On Tue, Sep 17, 2013 at 1:35 PM, Anis KADRI <[email protected]> wrote: > >> @maxw Did you create a user account with plugman adduser ? I do not >> see you in the users' list. >> >> Shazron: Very good point. We can always instruct those users to clone >> a 3.0.0 compatible branch from the repositories and install that. >> Maybe we can even update the tools to add the ability to clone from >> any branch (or maybe it's in there already ? I know it's in there for >> dependencies). >> >> On Tue, Sep 17, 2013 at 1:30 PM, Shazron <[email protected]> wrote: >> > I'm all for using master as the branch that we do development on, but if >> we >> > switch, that will mean anyone on existing cordova v3.0.0 will get broken >> > plugins, correct? >> > >> > >> > On Tue, Sep 17, 2013 at 1:25 PM, Steven Gill <[email protected]> >> wrote: >> > >> >> What would the command look like to install it if we aren't using git >> urls? >> >> cordova plugin add camera? Would it automatically take the latest >> version >> >> off the registery? >> >> >> >> I like the idea of working on master and tagging a plugin when it is >> ready >> >> to be published. >> >> >> >> >> >> >> >> >> >> On Tue, Sep 17, 2013 at 1:21 PM, Anis KADRI <[email protected]> >> wrote: >> >> >> >> > As far as I understand and following this documentation: >> >> > >> >> > >> >> > >> >> >> http://cordova.apache.org/docs/en/3.0.0/guide_cli_index.md.html#The%20Command-line%20Interface >> >> > >> >> > Plugins are currently fetched using git from origin/master. It is a >> >> > major problem in my opinion. The main reason (but there are many) is >> >> > that any commit to master can potentially break plugins. Yes, we can >> >> > do a dev branch but some people are forgetful and might commit to >> >> > master anyway. I think the proper development process for plugins >> >> > should be: >> >> > - Always commit to master >> >> > - When you're ready to release a plugin: update the version, tag it >> >> > and publish it to the cordova registry. >> >> > - Users can then install the latest version without having to remember >> >> > a git URL and without worrying about getting a broken plugin. >> >> > >> >> > Ideally, every Cordova committer should be granted the right to >> >> > publish to the registry. Right now, I've only added Andrew Grieve (who >> >> > is having issues publishing atm...). If anybody wants to be added, let >> >> > me know. >> >> > >> >> > Does that sound good to everyone? >> >> > >> >> > -a >> >> > >> >> >>
