You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by James Long <jl...@mozilla.com> on 2014/02/06 22:50:58 UTC
Release schedule for core plugins?
Hey guys,
I'm James from Mozilla and I'm working on Firefox OS support in
Cordova. A bunch of stuff has changed recently with the 3.4 release,
notably the plugins being pulled out and more separated. This is all
good stuff.
My team has a question, though. What exactly is the process for
pushing fixes to plugins? I think I've been told, but I forget and
we've had a hard time getting a few fixes out quickly recently. We
want to make sure that we can push stuff somewhat quickly so
developers aren't sitting on broken plugins for a while.
I've seen this page: http://wiki.apache.org/cordova/CommitterWorkflow
Under "which branch to commit to" for plugins it says:
"Commit all changes to branch: dev
* Through Cordova 3.0, plugman installed from master, which means we
couldn't use master for development.
* Post Cordova 3.0, plugman has support for a registry..."
The last line doesn't really explain anything. What do you mean by
registry? Can we start using master for development now? Does the
registry use tags or something to pull specific versions? It would be
great if `cordova plugin add` had a way to say "pull from HEAD, I want
the latest and greatest". If we can't get our fixes out quickly, we
need to tell developers to install plugins from our own repos and that
gets confusing.
Hope that wasn' too long-winded, thanks!
- James
Re: Release schedule for core plugins?
Posted by Steven Gill <st...@gmail.com>.
Hey James,
Our release process for plugins can be found at
https://wiki.apache.org/cordova/StepsForPluginRelease
org.apache.cordova.* is reserved for apache cordova commiters only.
We can merge as often as once a week to once a month. Just depends on need.
I just completed a dev -> master merge + plugins.cordova.io release. FFOS
plugins support should be good to go now on the plugins you guys added
support for.
On Mon, Feb 10, 2014 at 2:55 PM, James Long <jl...@mozilla.com> wrote:
> Thanks Shazron, that helps a lot. A few more quick questions:
>
> * How does permissions work with plugman? What would happen if I tried
> to publish a org.apache.cordova.* plugin?
>
> * How often do you guys merge dev -> master?
>
> I'm glad to you that you can specific branches and tags, I didn't know
> that!
>
> - James
>
> On Fri, Feb 7, 2014 at 4:45 PM, Shazron <sh...@gmail.com> wrote:
> > I don't think you can use master for development yet. Master is for the
> > version that gets published to the registry (and dev merges into master
> > when the time comes).
> >
> > If you run "plugman" without any args you can see the help regarding
> > publish:
> >
> > plugman publish <directory>
> >
> > Just make sure your plugin.xml is up to date (version numbers, etc).
> >
> > Users can always do a direct plugin add by for example doing:
> >
> > cordova plugin add
> > https://github.com/apache/cordova-labs.git#branch:folder
> >
> > ("#" signifies the branch to checkout, ":" the subfolder to grab from the
> > root)
> >
> > To grab a tag:
> >
> > cordova plugin add https://github.com/apache/cordova-labs.git@tag
> >
> >
> >
> >
> > On Thu, Feb 6, 2014 at 1:50 PM, James Long <jl...@mozilla.com> wrote:
> >
> >> Hey guys,
> >>
> >> I'm James from Mozilla and I'm working on Firefox OS support in
> >> Cordova. A bunch of stuff has changed recently with the 3.4 release,
> >> notably the plugins being pulled out and more separated. This is all
> >> good stuff.
> >>
> >> My team has a question, though. What exactly is the process for
> >> pushing fixes to plugins? I think I've been told, but I forget and
> >> we've had a hard time getting a few fixes out quickly recently. We
> >> want to make sure that we can push stuff somewhat quickly so
> >> developers aren't sitting on broken plugins for a while.
> >>
> >> I've seen this page: http://wiki.apache.org/cordova/CommitterWorkflow
> >>
> >> Under "which branch to commit to" for plugins it says:
> >>
> >> "Commit all changes to branch: dev
> >> * Through Cordova 3.0, plugman installed from master, which means we
> >> couldn't use master for development.
> >> * Post Cordova 3.0, plugman has support for a registry..."
> >>
> >>
> >> The last line doesn't really explain anything. What do you mean by
> >> registry? Can we start using master for development now? Does the
> >> registry use tags or something to pull specific versions? It would be
> >> great if `cordova plugin add` had a way to say "pull from HEAD, I want
> >> the latest and greatest". If we can't get our fixes out quickly, we
> >> need to tell developers to install plugins from our own repos and that
> >> gets confusing.
> >>
> >> Hope that wasn' too long-winded, thanks!
> >>
> >> - James
> >>
>
Re: Release schedule for core plugins?
Posted by James Long <jl...@mozilla.com>.
Thanks Shazron, that helps a lot. A few more quick questions:
* How does permissions work with plugman? What would happen if I tried
to publish a org.apache.cordova.* plugin?
* How often do you guys merge dev -> master?
I'm glad to you that you can specific branches and tags, I didn't know that!
- James
On Fri, Feb 7, 2014 at 4:45 PM, Shazron <sh...@gmail.com> wrote:
> I don't think you can use master for development yet. Master is for the
> version that gets published to the registry (and dev merges into master
> when the time comes).
>
> If you run "plugman" without any args you can see the help regarding
> publish:
>
> plugman publish <directory>
>
> Just make sure your plugin.xml is up to date (version numbers, etc).
>
> Users can always do a direct plugin add by for example doing:
>
> cordova plugin add
> https://github.com/apache/cordova-labs.git#branch:folder
>
> ("#" signifies the branch to checkout, ":" the subfolder to grab from the
> root)
>
> To grab a tag:
>
> cordova plugin add https://github.com/apache/cordova-labs.git@tag
>
>
>
>
> On Thu, Feb 6, 2014 at 1:50 PM, James Long <jl...@mozilla.com> wrote:
>
>> Hey guys,
>>
>> I'm James from Mozilla and I'm working on Firefox OS support in
>> Cordova. A bunch of stuff has changed recently with the 3.4 release,
>> notably the plugins being pulled out and more separated. This is all
>> good stuff.
>>
>> My team has a question, though. What exactly is the process for
>> pushing fixes to plugins? I think I've been told, but I forget and
>> we've had a hard time getting a few fixes out quickly recently. We
>> want to make sure that we can push stuff somewhat quickly so
>> developers aren't sitting on broken plugins for a while.
>>
>> I've seen this page: http://wiki.apache.org/cordova/CommitterWorkflow
>>
>> Under "which branch to commit to" for plugins it says:
>>
>> "Commit all changes to branch: dev
>> * Through Cordova 3.0, plugman installed from master, which means we
>> couldn't use master for development.
>> * Post Cordova 3.0, plugman has support for a registry..."
>>
>>
>> The last line doesn't really explain anything. What do you mean by
>> registry? Can we start using master for development now? Does the
>> registry use tags or something to pull specific versions? It would be
>> great if `cordova plugin add` had a way to say "pull from HEAD, I want
>> the latest and greatest". If we can't get our fixes out quickly, we
>> need to tell developers to install plugins from our own repos and that
>> gets confusing.
>>
>> Hope that wasn' too long-winded, thanks!
>>
>> - James
>>
Re: Release schedule for core plugins?
Posted by Shazron <sh...@gmail.com>.
I don't think you can use master for development yet. Master is for the
version that gets published to the registry (and dev merges into master
when the time comes).
If you run "plugman" without any args you can see the help regarding
publish:
plugman publish <directory>
Just make sure your plugin.xml is up to date (version numbers, etc).
Users can always do a direct plugin add by for example doing:
cordova plugin add
https://github.com/apache/cordova-labs.git#branch:folder
("#" signifies the branch to checkout, ":" the subfolder to grab from the
root)
To grab a tag:
cordova plugin add https://github.com/apache/cordova-labs.git@tag
On Thu, Feb 6, 2014 at 1:50 PM, James Long <jl...@mozilla.com> wrote:
> Hey guys,
>
> I'm James from Mozilla and I'm working on Firefox OS support in
> Cordova. A bunch of stuff has changed recently with the 3.4 release,
> notably the plugins being pulled out and more separated. This is all
> good stuff.
>
> My team has a question, though. What exactly is the process for
> pushing fixes to plugins? I think I've been told, but I forget and
> we've had a hard time getting a few fixes out quickly recently. We
> want to make sure that we can push stuff somewhat quickly so
> developers aren't sitting on broken plugins for a while.
>
> I've seen this page: http://wiki.apache.org/cordova/CommitterWorkflow
>
> Under "which branch to commit to" for plugins it says:
>
> "Commit all changes to branch: dev
> * Through Cordova 3.0, plugman installed from master, which means we
> couldn't use master for development.
> * Post Cordova 3.0, plugman has support for a registry..."
>
>
> The last line doesn't really explain anything. What do you mean by
> registry? Can we start using master for development now? Does the
> registry use tags or something to pull specific versions? It would be
> great if `cordova plugin add` had a way to say "pull from HEAD, I want
> the latest and greatest". If we can't get our fixes out quickly, we
> need to tell developers to install plugins from our own repos and that
> gets confusing.
>
> Hope that wasn' too long-winded, thanks!
>
> - James
>