Julio, I would be happy to pair with you on some plugin releases.
As you already noticed, the release processes via coho need some
serious work now that we are on GitHub issues instead of JIRA, so we
have some additional work ahead of us.
First step would be to identify which plugin to start
I believe the issue with the pending releases is not that nobody is
performing the release task. There are still implementation details
being worked on if I'm not mistaken.
The next release will supposedly introduce several major breaking
changes, which have to be prepared for thoroughly.
Steven, thanks so much for all your help getting the plugins released.
-Original Message-
From: Murat Sutunc [mailto:mura...@microsoft.com]
Sent: Wednesday, May 6, 2015 1:42 PM
To: dev@cordova.apache.org
Subject: RE: Plugins release prep: Cherry-picking plugin updates
Hey, took me
Hey, took me a while but we're good to go with:
Camera, device-motion, dialogs and vibration.
Thanks!
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Wednesday, May 6, 2015 12:16 PM
To: dev@cordova.apache.org
Subject: Re: Plugins release prep: Cherry-picking
I haven't heard back. Should I move forward with those 5 plugins?
file-transfer, device-motion, dialogs, vibration, and camera.
I will update the process to support specific plugins release (instead of
all plugins) as I work through it.
On Tue, May 5, 2015 at 12:29 PM, Jesse
Hey guys,
I can help you out. The process is designed for all plugins but it is
pretty easy to do it for just a few. I've done it many times.
If changes are on master, they shouldn't be incomplete. Any known problem
with release the master branch of those plugins?
We could cherry-pick, but it
+ file-transfer so we can resolve CB-8951
@purplecabbage
risingj.com
On Tue, May 5, 2015 at 12:19 PM, Steven Gill stevengil...@gmail.com wrote:
Hey guys,
I can help you out. The process is designed for all plugins but it is
pretty easy to do it for just a few. I've done it many times.
If
wait wait, a cordova organization on github with push access!? Thats like,
useful! (and blasphemy)
On Thu, Aug 7, 2014 at 9:33 PM, Andrew Grieve agri...@chromium.org wrote:
LGTM
On Thu, Aug 7, 2014 at 7:17 PM, Steven Gill stevengil...@gmail.com
wrote:
Please review and send PRs for
LGTM
On Fri, Aug 8, 2014 at 8:22 AM, Michal Mocny mmo...@chromium.org wrote:
wait wait, a cordova organization on github with push access!? Thats like,
useful! (and blasphemy)
On Thu, Aug 7, 2014 at 9:33 PM, Andrew Grieve agri...@chromium.org
wrote:
LGTM
On Thu, Aug 7, 2014 at
Hahaha. Michal, we pretty much only use it to preview blog posts board
reports. I sent you an invite to it.
On Fri, Aug 8, 2014 at 9:57 AM, Bryan Higgins br...@bryanhiggins.net
wrote:
LGTM
On Fri, Aug 8, 2014 at 8:22 AM, Michal Mocny mmo...@chromium.org wrote:
wait wait, a cordova
Typo in
Ubuntu: fix compler warnings
Axel
Am 08.08.2014 00:18 schrieb Steven Gill stevengil...@gmail.com:
Please review and send PRs for changes. I can also add you to the repo if
you want to edit directly on github and not worry about the PR.
Fixed! Thanks
On Fri, Aug 8, 2014 at 11:58 AM, Axel Nennker ignisvul...@gmail.com wrote:
Typo in
Ubuntu: fix compler warnings
Axel
Am 08.08.2014 00:18 schrieb Steven Gill stevengil...@gmail.com:
Please review and send PRs for changes. I can also add you to the repo if
you want to
LGTM
On Thu, Aug 7, 2014 at 7:17 PM, Steven Gill stevengil...@gmail.com wrote:
Please review and send PRs for changes. I can also add you to the repo if
you want to edit directly on github and not worry about the PR.
Nice work. Clean up extended notes and added re-did call-out of file
changes: https://github.com/cordova/apache-blog-posts/pull/5
On Fri, Jun 6, 2014 at 7:36 PM, Steven Gill stevengil...@gmail.com wrote:
Please review the blog post at
will be able to see
some outdated non-English documentation. Is that helpful?
-Original Message-
From: agri...@google.com [mailto:agri...@google.com] On Behalf Of Andrew
Grieve
Sent: Tuesday, 11 February 2014 2:35 PM
To: dev
Subject: Re: Plugins Release!
Feedback definitely welcome
: +415.787.4589 | ldel...@apache.org | |
ldel...@us.ibm.com | lisaseacat.com | |
From: Andrew Grieve agri...@chromium.org
To: dev dev@cordova.apache.org
Date: 02/11/2014 10:56 AM
Subject:Re: Plugins Release!
Sent by:agri...@google.com
For now, that's correct. Eventually
shipped.
http://cordova.apache.org/news/2014/02/10/plugins-release.html
On Sat, Feb 8, 2014 at 8:43 AM, Andrew Grieve agri...@chromium.org wrote:
ship it.
On Fri, Feb 7, 2014 at 7:35 PM, Steven Gill stevengil...@gmail.com
wrote:
ship it?
On Fri, Feb 7, 2014 at 12:03 PM, Steven
it here:
http://cordova.apache.org/docs/en/3.3.0/cordova_camera_camera.md.html#Camera
From: Steven Gill stevengil...@gmail.com
Sent: Monday, February 10, 2014 5:53 PM
To: dev@cordova.apache.org
Subject: Re: Plugins Release!
shipped.
http://cordova.apache.org
not see it here:
http://cordova.apache.org/docs/en/3.3.0/cordova_camera_camera.md.html#Camera
From: Steven Gill stevengil...@gmail.com
Sent: Monday, February 10, 2014 5:53 PM
To: dev@cordova.apache.org
Subject: Re: Plugins Release!
shipped.
http
: Re: Plugins Release!
Feedback definitely welcome in this department.
For the 3.4.0 release, the main docs for plugins will look like:
http://cordova.apache.org/docs/en/edge/cordova_plugins_pluginapis.md.html#Plugin%20APIs
On Mon, Feb 10, 2014 at 10:07 PM, Ray Camden rayca...@adobe.com wrote:
: Tuesday, 11 February 2014 2:35 PM
To: dev
Subject: Re: Plugins Release!
Feedback definitely welcome in this department.
For the 3.4.0 release, the main docs for plugins will look like:
http://cordova.apache.org/docs/en/edge/cordova_plugins_pluginapis.md.html#Plugin%20APIs
On Mon, Feb 10, 2014 at 10:07
ship it.
On Fri, Feb 7, 2014 at 7:35 PM, Steven Gill stevengil...@gmail.com wrote:
ship it?
On Fri, Feb 7, 2014 at 12:03 PM, Steven Gill stevengil...@gmail.com
wrote:
Thanks for the feedback Ian! Just waiting on the SHIP IT
Updated blog below:
---
layout: post
author:
Thanks for the feedback Ian! Just waiting on the SHIP IT
Updated blog below:
---
layout: post
author:
name: Steve Gill
url: https://twitter.com/stevesgill
title: Plugins Release: Feb 7, 2014
categories: news
tags: release
---
The following plugins were updated today:
*
ship it?
On Fri, Feb 7, 2014 at 12:03 PM, Steven Gill stevengil...@gmail.com wrote:
Thanks for the feedback Ian! Just waiting on the SHIP IT
Updated blog below:
---
layout: post
author:
name: Steve Gill
url: https://twitter.com/stevesgill
title: Plugins Release: Feb 7, 2014
it! I think File still needs some work:
https://issues.apache.org/jira/browse/CB-5974
On Tue, Feb 4, 2014 at 3:18 PM, Herm Wong kingoftheo...@hotmail.com
wrote:
Sounds good to me!
From: agri...@chromium.org
Date: Tue, 4 Feb 2014 14:35:01 -0500
Subject: Re: Plugins Release!
To: dev
+1 to this.
How about this addition: if the setting isn't explicitly declared in
config.xml, log a warning but still default to exactly where they are now.
On Feb 5, 2014, at 10:50 AM, Ian Clelland iclell...@chromium.org wrote:
So this proposal would be:
- Don't revert the changes made on
I've taken a first pass at the file plugin (I'll probably revisit it in the
morning and think it's terrible :) )
On Thu, Feb 6, 2014 at 4:44 PM, Steven Gill stevengil...@gmail.com wrote:
Okay, I have a blog post ready to review. I could use some help with adding
more content about the file
+1 for a warning..
Warnings are the precursors to education - me, just now
On 07/02/2014 11:55 am, Marcel Kinard cmarc...@gmail.com wrote:
+1 to this.
How about this addition: if the setting isn't explicitly declared in
config.xml, log a warning but still default to exactly where they are
-1 to merging reads. That just sounds like a horrible thing to debug.
+1 to 'go big or go home'. Break it now. Break it obviously.
On Tue, Feb 4, 2014 at 11:45 PM, Josh Soref jso...@blackberry.com wrote:
Is it impossible to have reads merged from both locations, but writes go
to the new
On 5 February 2014 13:20, David Kemp drk...@google.com wrote:
-1 to merging reads. That just sounds like a horrible thing to debug.
Seems to me that developers using the plugin will have to implement
something similar in order to make it easier for their users.
Would it not be better to spend
My concern with any automated fix is that we have no idea what files belong
to an app.
The default is to just toss everything in the root.
Files may be user data that is shared between apps, config files or temp
files. The developer probably knows what to migrate - we don't.\
On Wed, Feb 5, 2014
On Tue, Feb 4, 2014 at 11:45 PM, Josh Soref jso...@blackberry.com wrote:
Is it impossible to have reads merged from both locations, but writes go
to the new location, and when a write completes in the new location, delete
the old one?
It might be. The File API doesn't impose any sort of
On 5 February 2014 14:55, David Kemp drk...@google.com wrote:
My concern with any automated fix is that we have no idea what files belong
to an app.
The default is to just toss everything in the root.
Files may be user data that is shared between apps, config files or temp
files. The
Imagine a hypothetical implementation which works like this:
Consumer asks for a file, we don't find it in Library, nor is the we're
migrating file, we create the we're migrating file, it's present in Root.
We start a copy in the background and return some file handle (probably a
proxy). Any
Honestly, my opinion on this: Leave the default as-is for now. We've just
made huge changes to the API, which may have bugs / implications we haven't
fully thought through. Lets let a subset of users upgrade to the new
$MAJOR version, and a subset of those add the new preference. In a later
I also think we should break it now. It's not as if we have never broken
anything before... keeping backward compatibility should anyways be
preferred but in this case I think it would cause more trouble than it
would solve.
I say don't write any migration tools but document the changes in
On Wed, Feb 5, 2014 at 10:29 AM, Anis KADRI anis.ka...@gmail.com wrote:
I also think we should break it now. It's not as if we have never broken
anything before... keeping backward compatibility should anyways be
preferred but in this case I think it would cause more trouble than it
would
On Wed, Feb 5, 2014 at 10:25 AM, Michal Mocny mmo...@chromium.org wrote:
Honestly, my opinion on this: Leave the default as-is for now. We've just
made huge changes to the API, which may have bugs / implications we haven't
fully thought through.
That's a really good point. If we do this
I couldn't have said it better myself. -1 to just break it.
On Wed, Feb 5, 2014 at 8:00 AM, Tommy Williams to...@devgeeks.org wrote:
-1 to just break it
Developers using Cordova still are frequently having to deal with massive
breaking changes every few releases. Developing and (even more
Of course, while writing my rant, Ian has summarized a great proposal.
+1 to the below!
On 06/02/2014 2:51 am, Ian Clelland iclell...@chromium.org wrote:
On Wed, Feb 5, 2014 at 10:25 AM, Michal Mocny mmo...@chromium.org wrote:
Honestly, my opinion on this: Leave the default as-is for now.
Agreed! I didn't see that either until now.
On Wed, Feb 5, 2014 at 8:04 AM, Tommy Williams to...@devgeeks.org wrote:
Of course, while writing my rant, Ian has summarized a great proposal.
+1 to the below!
On 06/02/2014 2:51 am, Ian Clelland iclell...@chromium.org wrote:
On Wed, Feb 5, 2014
I think this approach is our best path forward right now. There's no
immediate need to break apps for developers; it was a convenient time in
the development of the plugin, but we can easily wait for another
convenient time. There seems to be no compelling reason to couple a
breaking change with
Joe - I appreciate your effort and your input, but I don't appreciate
hostility on this list from anyone, including you.
This is a public list, and I see nothing wrong with sebb's email in this
thread.
If you are at the point that you don't want to receive emails from sebb,
then I would ask that
+1 to Ian's proposal
@purplecabbage
risingj.com
On Wed, Feb 5, 2014 at 1:33 PM, Andrew Grieve agri...@chromium.org wrote:
Joe - I appreciate your effort and your input, but I don't appreciate
hostility on this list from anyone, including you.
This is a public list, and I see nothing wrong
It sounds like a good plan indeed. I would encourage our users to migrate
to the new locations as soon as they can. 12 months is an acceptable
migration window I believe.
+1 to Ian's proposal.
On Wed, Feb 5, 2014 at 1:43 PM, Jesse purplecabb...@gmail.com wrote:
+1 to Ian's proposal
I am going to take the silence as lazy consensus. I will make sure to
include the new file plugin as well.
I will make sure to have a blog post of changes to review before I publish.
-Steve
On Mon, Feb 3, 2014 at 10:33 AM, Steven Gill stevengil...@gmail.com wrote:
Hey All,
What is the
Sounds good!
On Tue, Feb 4, 2014 at 2:19 PM, Steven Gill stevengil...@gmail.com wrote:
I am going to take the silence as lazy consensus. I will make sure to
include the new file plugin as well.
I will make sure to have a blog post of changes to review before I publish.
-Steve
On Mon,
Sounds good to me!
From: agri...@chromium.org
Date: Tue, 4 Feb 2014 14:35:01 -0500
Subject: Re: Plugins Release!
To: dev@cordova.apache.org
Sounds good!
On Tue, Feb 4, 2014 at 2:19 PM, Steven Gill stevengil...@gmail.com wrote:
I am going to take the silence as lazy consensus. I
Don't do it! I think File still needs some work:
https://issues.apache.org/jira/browse/CB-5974
On Tue, Feb 4, 2014 at 3:18 PM, Herm Wong kingoftheo...@hotmail.com wrote:
Sounds good to me!
From: agri...@chromium.org
Date: Tue, 4 Feb 2014 14:35:01 -0500
Subject: Re: Plugins Release
at 3:18 PM, Herm Wong kingoftheo...@hotmail.com
wrote:
Sounds good to me!
From: agri...@chromium.org
Date: Tue, 4 Feb 2014 14:35:01 -0500
Subject: Re: Plugins Release!
To: dev@cordova.apache.org
Sounds good!
On Tue, Feb 4, 2014 at 2:19 PM, Steven Gill stevengil...@gmail.com
Is it impossible to have reads merged from both locations, but writes go to the
new location, and when a write completes in the new location, delete the old
one?
No one's announced their intent to do one yet that I've seen.
On Thu, Jan 16, 2014 at 2:17 PM, Herm Wong kingoftheo...@hotmail.comwrote:
Are we planning on a plugin release soon?
There have been quite a few commits for FirefoxOS that need to be released
into the main branch.
Going to try and do this today :)
On Fri, Dec 20, 2013 at 1:33 PM, Ian Clelland iclell...@chromium.orgwrote:
That sounds reasonable. There isn't a huge rush on it.
On Fri, Dec 20, 2013 at 10:54 AM, Andrew Grieve agri...@chromium.org
wrote:
Well, I didn't do this yesterday and don't want
Well, I didn't do this yesterday and don't want to do a Friday release, so
I'll do this Monday instead.
I'll skip File plugin again until someone can test WP.
On Thu, Dec 19, 2013 at 1:40 AM, purplecabbage purplecabb...@gmail.comwrote:
I have not. Someone needs to test the impact on windows
That sounds reasonable. There isn't a huge rush on it.
On Fri, Dec 20, 2013 at 10:54 AM, Andrew Grieve agri...@chromium.orgwrote:
Well, I didn't do this yesterday and don't want to do a Friday release, so
I'll do this Monday instead.
I'll skip File plugin again until someone can test WP.
@cordova.apache.org
Subject: Re: Plugins Release today
Thanks Steve!
On Wed, Dec 4, 2013 at 11:07 PM, Andrew Grieve agri...@chromium.org
wrote:
Great job! Thanks indeed!
On Wed, Dec 4, 2013 at 11:01 PM, Brian LeRoux b...@brian.io wrote:
thx Steve!
On Thu, Dec 5, 2013 at 2:47 PM
. Thank you!
-Sergey
-Original Message-
From: Steven Gill [mailto:stevengil...@gmail.com]
Sent: Thursday, December 5, 2013 10:52 PM
To: dev@cordova.apache.org
Subject: Re: Plugins Release today
Hey Sergey,
We can still add the lines. The File plugin didn't get released with this
release. Feel
You can definitely do an automated build on demand, but the interesting
part is specifying exactly what to build.
Currently a build is made up of a bunch of repos at one tag, and some other
repos at another tag.
We would need to have a well defined way to specify which tag for each repo.
example:
On Wed, Dec 4, 2013 at 2:54 PM, David Kemp drk...@google.com wrote:
You can definitely do an automated build on demand, but the interesting
part is specifying exactly what to build.
Currently a build is made up of a bunch of repos at one tag, and some other
repos at another tag.
We would
Plugins have been released!
http://cordova.apache.org/news/2013/12/04/plugins-release.html
https://twitter.com/apachecordova/status/408441655222476800
device-motion and battery-status haven't been published yet due to a error
I ran into with plugman publish. I have pinged Anis to take a look.
thx Steve!
On Thu, Dec 5, 2013 at 2:47 PM, Steven Gill stevengil...@gmail.com wrote:
Plugins have been released!
http://cordova.apache.org/news/2013/12/04/plugins-release.html
https://twitter.com/apachecordova/status/408441655222476800
device-motion and battery-status haven't been
Great job! Thanks indeed!
On Wed, Dec 4, 2013 at 11:01 PM, Brian LeRoux b...@brian.io wrote:
thx Steve!
On Thu, Dec 5, 2013 at 2:47 PM, Steven Gill stevengil...@gmail.com
wrote:
Plugins have been released!
http://cordova.apache.org/news/2013/12/04/plugins-release.html
Hey Steven,
File is close to being ready, but I haven't merged in my Android code yet,
and I want to add some more tests, given how critical the plugin is. I'm
not comfortable with it going to master yet. If you want, I can pull it out
of dev and put it on another branch. (There have been some
Thanks for filling me in on the state!
Is it just File that isn't ready? File-transfer is good?
I don't think it is worth it to rip out the code from dev, especially if it
is almost ready. I will hold off releasing file with this plugins release.
We can aim to get a new version of file out next
Plugins have been released for this week.
http://cordova.apache.org/news/2013/10/10/plugins-release.html
On Wed, Oct 9, 2013 at 1:34 PM, Andrew Grieve agri...@chromium.org wrote:
Btw - sounds good about plugin release!
No need to add the labs plugins (as you said, they are already there),
Just as a side note:
this release should also fix file-transfer on WP7 WP8 =
https://issues.apache.org/jira/browse/CB-4668
https://issues.apache.org/jira/browse/CB-4717
Best,
Wolfgang
Am 2013-10-11 01:25, schrieb Steven Gill:
Plugins have been released for this week.
So plugins that are on cordova-labs will not be included in my release this
week.
It seems like people have been publishing the cordova-labs plugins
independently so far from the (bi)-weekly plugins release.
Plugins in cordova-labs include:
keyboard (published to registry)
websql (published to
An alternative to new repos for all of them is to put them in their
platform repos. So far none of them have multiple platforms.
I'd like to wait a while before creating too many more plugin repositories,
just until the number of plugins levels out.
On Wed, Oct 9, 2013 at 3:32 PM, Steven Gill
Btw - sounds good about plugin release!
No need to add the labs plugins (as you said, they are already there), but
it would be good to mention them in your blog post (just the published
ones: keyboard, websql, statusbar).
On Wed, Oct 9, 2013 at 4:32 PM, Andrew Grieve agri...@chromium.org wrote:
I'll want to have a hand in the next release of the tools, because of the
refactoring.
Braden
On Mon, Oct 7, 2013 at 2:51 PM, Steven Gill stevengil...@gmail.com wrote:
Last week as we were finishing off the release, I remember their was some
interest in doing another plugins release this
Er, I didn't actually say: for the tools, not yet, maybe later this week.
Braden
On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson bra...@chromium.orgwrote:
I'll want to have a hand in the next release of the tools, because of the
refactoring.
Braden
On Mon, Oct 7, 2013 at 2:51 PM,
I remember someone said the refactoring broke ffos. Not sure if that's
fixed yet?
Other than that, sounds great to release both this week. Would be good to
do them together so as to have a shared blog post.
On Mon, Oct 7, 2013 at 3:04 PM, Braden Shepherdson bra...@chromium.orgwrote:
Er, I
If we want to do CLI/Plugman, we definitely will need to do more testing
and fix some things (like FFOS). I think we also need to make sure that
some of the changes that went into cordova-3.1.x branches also ended up in
the refactored master branches.
I will plan on doing the plugins release
https://issues.apache.org/jira/browse/CB-5010
On Mon, Oct 7, 2013 at 3:24 PM, Steven Gill stevengil...@gmail.com wrote:
If we want to do CLI/Plugman, we definitely will need to do more testing
and fix some things (like FFOS). I think we also need to make sure that
some of the changes that
Can we serve the html doc somewhere? I'd rather not read a diff on html.
On 26 September 2013 18:08, Steven Gill stevengil...@gmail.com wrote:
Looks like I forgot to click publish on the review page. I also found a
bunch of spelling mistakes I made in my rush to create this. I just fixed
best to review the .md file instead.
I don't think there's a good way to host it somewhere, other than for you
to download and apply the patch, and run rake serve yourself.
On Fri, Sep 27, 2013 at 7:49 PM, Tim Kim timki...@gmail.com wrote:
Can we serve the html doc somewhere? I'd rather not
Does everyone have access to this? I get:
You don't have access to this review request.
This review request is private. You must be a requested reviewer, either
directly or on a requested group, and have permission to access the
repository in order to view this review request.
On Thu, Sep 26,
You don't have access to this review request.
This review request is private. You must be a requested reviewer, either
directly or on a requested group, and have permission to access the
repository in order to view this review request.
Ya, same here
On 26 September 2013 16:37, Shazron
I have no idea how this review stuff works. I will post the blog here
On Sep 26, 2013 4:59 PM, Tim Kim timki...@gmail.com wrote:
You don't have access to this review request.
This review request is private. You must be a requested reviewer, either
directly or on a requested group, and
Today we are doing a big plugin release in preperation for Apache Cordova
3.1.0 which is scheduled to come out next week.
The main change for this release is removing core from all of the plugin ID
fields. This was done to make installing plugins easier in 3.1.0. We are
switching over to using
Looks like I forgot to click publish on the review page. I also found a
bunch of spelling mistakes I made in my rush to create this. I just fixed
them and uploaded a new diff. The review site should be available for all
now to leave feedback.
On Thu, Sep 26, 2013 at 5:42 PM, Steven Gill
81 matches
Mail list logo
