You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Anis KADRI <an...@gmail.com> on 2013/09/17 22:21:15 UTC
About plugins in 3.1
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
Re: About plugins in 3.1
Posted by Anis KADRI <an...@gmail.com>.
$ cordova plugin add org.apache.cordova.core.camera # cuz we decided
to use package names for IDs to avoid collisions
Yes, it would take the latest version but you can specify which
version you want by running
$ cordova plugin add org.apache.cordova.core.camera@x.x.x
On Tue, Sep 17, 2013 at 1:25 PM, Steven Gill <st...@gmail.com> 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 <an...@gmail.com> 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
>>
Re: About plugins in 3.1
Posted by Steven Gill <st...@gmail.com>.
Thanks!
On Fri, Sep 27, 2013 at 12:31 AM, Anis KADRI <an...@gmail.com> wrote:
> Plugins have been published! Time to test!
>
> On Fri, Sep 27, 2013 at 9:18 AM, Anis KADRI <an...@gmail.com> wrote:
> > I will publish them from master. There is an issue with permissions
> > right now :-/
> >
> > On Fri, Sep 27, 2013 at 5:03 AM, Steven Gill <st...@gmail.com>
> wrote:
> >> Plugins are ready to be published. I did plugman adduser. Can't publish
> >> plugins yet. Guessing Anis has to give me permission.
> >>
> >>
> >> On Tue, Sep 17, 2013 at 6:10 PM, Andrew Grieve <ag...@chromium.org>
> wrote:
> >>
> >>> The ability to clone from a branch/tag already exists. It didn't for
> 3.0,
> >>> but was added afterwards.
> >>>
> >>> I don't think there's much use in changing instructions to install from
> >>> git+tag urls when the registry exists anyways. The registry has
> >>> 3.0-compatible plugins in it, so that's a better solution.
> >>>
> >>> I do think we should wait some time before making the switch to
> developing
> >>> on master (and deleting the dev branches), since it'll take some time
> to
> >>> get the word out. There's even been some tools (yeoman & the like) that
> >>> have been written that hardcode in the git URLs.
> >>>
> >>> Definitely excited about this though! So much nicer!
> >>>
> >>>
> >>> On Tue, Sep 17, 2013 at 5:20 PM, Anis KADRI <an...@gmail.com>
> wrote:
> >>>
> >>> > @maxw: done!
> >>> >
> >>> > On Tue, Sep 17, 2013 at 1:55 PM, Shazron <sh...@gmail.com> 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 <an...@gmail.com>
> >>> > 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 <sh...@gmail.com>
> 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 <
> >>> stevengill97@gmail.com>
> >>> > >> 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 <
> anis.kadri@gmail.com>
> >>> > >> 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
> >>> > >> >> >
> >>> > >> >>
> >>> > >>
> >>> >
> >>>
>
Re: About plugins in 3.1
Posted by Anis KADRI <an...@gmail.com>.
Plugins have been published! Time to test!
On Fri, Sep 27, 2013 at 9:18 AM, Anis KADRI <an...@gmail.com> wrote:
> I will publish them from master. There is an issue with permissions
> right now :-/
>
> On Fri, Sep 27, 2013 at 5:03 AM, Steven Gill <st...@gmail.com> wrote:
>> Plugins are ready to be published. I did plugman adduser. Can't publish
>> plugins yet. Guessing Anis has to give me permission.
>>
>>
>> On Tue, Sep 17, 2013 at 6:10 PM, Andrew Grieve <ag...@chromium.org> wrote:
>>
>>> The ability to clone from a branch/tag already exists. It didn't for 3.0,
>>> but was added afterwards.
>>>
>>> I don't think there's much use in changing instructions to install from
>>> git+tag urls when the registry exists anyways. The registry has
>>> 3.0-compatible plugins in it, so that's a better solution.
>>>
>>> I do think we should wait some time before making the switch to developing
>>> on master (and deleting the dev branches), since it'll take some time to
>>> get the word out. There's even been some tools (yeoman & the like) that
>>> have been written that hardcode in the git URLs.
>>>
>>> Definitely excited about this though! So much nicer!
>>>
>>>
>>> On Tue, Sep 17, 2013 at 5:20 PM, Anis KADRI <an...@gmail.com> wrote:
>>>
>>> > @maxw: done!
>>> >
>>> > On Tue, Sep 17, 2013 at 1:55 PM, Shazron <sh...@gmail.com> 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 <an...@gmail.com>
>>> > 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 <sh...@gmail.com> 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 <
>>> stevengill97@gmail.com>
>>> > >> 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 <an...@gmail.com>
>>> > >> 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
>>> > >> >> >
>>> > >> >>
>>> > >>
>>> >
>>>
Re: About plugins in 3.1
Posted by Anis KADRI <an...@gmail.com>.
I will publish them from master. There is an issue with permissions
right now :-/
On Fri, Sep 27, 2013 at 5:03 AM, Steven Gill <st...@gmail.com> wrote:
> Plugins are ready to be published. I did plugman adduser. Can't publish
> plugins yet. Guessing Anis has to give me permission.
>
>
> On Tue, Sep 17, 2013 at 6:10 PM, Andrew Grieve <ag...@chromium.org> wrote:
>
>> The ability to clone from a branch/tag already exists. It didn't for 3.0,
>> but was added afterwards.
>>
>> I don't think there's much use in changing instructions to install from
>> git+tag urls when the registry exists anyways. The registry has
>> 3.0-compatible plugins in it, so that's a better solution.
>>
>> I do think we should wait some time before making the switch to developing
>> on master (and deleting the dev branches), since it'll take some time to
>> get the word out. There's even been some tools (yeoman & the like) that
>> have been written that hardcode in the git URLs.
>>
>> Definitely excited about this though! So much nicer!
>>
>>
>> On Tue, Sep 17, 2013 at 5:20 PM, Anis KADRI <an...@gmail.com> wrote:
>>
>> > @maxw: done!
>> >
>> > On Tue, Sep 17, 2013 at 1:55 PM, Shazron <sh...@gmail.com> 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 <an...@gmail.com>
>> > 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 <sh...@gmail.com> 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 <
>> stevengill97@gmail.com>
>> > >> 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 <an...@gmail.com>
>> > >> 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
>> > >> >> >
>> > >> >>
>> > >>
>> >
>>
Re: About plugins in 3.1
Posted by Steven Gill <st...@gmail.com>.
Plugins are ready to be published. I did plugman adduser. Can't publish
plugins yet. Guessing Anis has to give me permission.
On Tue, Sep 17, 2013 at 6:10 PM, Andrew Grieve <ag...@chromium.org> wrote:
> The ability to clone from a branch/tag already exists. It didn't for 3.0,
> but was added afterwards.
>
> I don't think there's much use in changing instructions to install from
> git+tag urls when the registry exists anyways. The registry has
> 3.0-compatible plugins in it, so that's a better solution.
>
> I do think we should wait some time before making the switch to developing
> on master (and deleting the dev branches), since it'll take some time to
> get the word out. There's even been some tools (yeoman & the like) that
> have been written that hardcode in the git URLs.
>
> Definitely excited about this though! So much nicer!
>
>
> On Tue, Sep 17, 2013 at 5:20 PM, Anis KADRI <an...@gmail.com> wrote:
>
> > @maxw: done!
> >
> > On Tue, Sep 17, 2013 at 1:55 PM, Shazron <sh...@gmail.com> 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 <an...@gmail.com>
> > 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 <sh...@gmail.com> 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 <
> stevengill97@gmail.com>
> > >> 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 <an...@gmail.com>
> > >> 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
> > >> >> >
> > >> >>
> > >>
> >
>
Re: About plugins in 3.1
Posted by Andrew Grieve <ag...@chromium.org>.
The ability to clone from a branch/tag already exists. It didn't for 3.0,
but was added afterwards.
I don't think there's much use in changing instructions to install from
git+tag urls when the registry exists anyways. The registry has
3.0-compatible plugins in it, so that's a better solution.
I do think we should wait some time before making the switch to developing
on master (and deleting the dev branches), since it'll take some time to
get the word out. There's even been some tools (yeoman & the like) that
have been written that hardcode in the git URLs.
Definitely excited about this though! So much nicer!
On Tue, Sep 17, 2013 at 5:20 PM, Anis KADRI <an...@gmail.com> wrote:
> @maxw: done!
>
> On Tue, Sep 17, 2013 at 1:55 PM, Shazron <sh...@gmail.com> 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 <an...@gmail.com>
> 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 <sh...@gmail.com> 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 <st...@gmail.com>
> >> 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 <an...@gmail.com>
> >> 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
> >> >> >
> >> >>
> >>
>
Re: About plugins in 3.1
Posted by Anis KADRI <an...@gmail.com>.
@maxw: done!
On Tue, Sep 17, 2013 at 1:55 PM, Shazron <sh...@gmail.com> 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 <an...@gmail.com> 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 <sh...@gmail.com> 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 <st...@gmail.com>
>> 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 <an...@gmail.com>
>> 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
>> >> >
>> >>
>>
Re: About plugins in 3.1
Posted by Shazron <sh...@gmail.com>.
@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 <an...@gmail.com> 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 <sh...@gmail.com> 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 <st...@gmail.com>
> 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 <an...@gmail.com>
> 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
> >> >
> >>
>
Re: About plugins in 3.1
Posted by Max Woghiren <ma...@chromium.org>.
I hadn't, sorry. I have now!
On Tue, Sep 17, 2013 at 4:35 PM, Anis KADRI <an...@gmail.com> 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 <sh...@gmail.com> 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 <st...@gmail.com>
> 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 <an...@gmail.com>
> 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
> >> >
> >>
>
Re: About plugins in 3.1
Posted by Anis KADRI <an...@gmail.com>.
@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 <sh...@gmail.com> 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 <st...@gmail.com> 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 <an...@gmail.com> 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
>> >
>>
Re: About plugins in 3.1
Posted by Shazron <sh...@gmail.com>.
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 <st...@gmail.com> 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 <an...@gmail.com> 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
> >
>
Re: About plugins in 3.1
Posted by Steven Gill <st...@gmail.com>.
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 <an...@gmail.com> 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
>
Re: About plugins in 3.1
Posted by Max Woghiren <ma...@chromium.org>.
I agree that your proposed plugin flow makes good sense. The registry
solves this problem of potential broken plugins, but only as long as people
are getting plugins from there. The encouraged use of plugin dev branches
still has merit as long as people might be cloning plugin repos, though I
agree that the possibility of forgetting to push to dev is a problem.
Either way, please add me to the publisher list. :)
On Tue, Sep 17, 2013 at 4:21 PM, Anis KADRI <an...@gmail.com> 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
>