Re: [DISCUSS] Plugin release
https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md but I used the new undocumented automatic release script that fil created for this past one. I'll document it up for this next release On Fri, Sep 22, 2017 at 3:04 PM, Simon MacDonaldwrote: > Yeah, we should be doing another plugins release soon. We have: > > cordova-plugin-status-bar > cordova-plugin-file-transfer > > Needing releases. > > Steve, is the release process documented anywhere so you don't have to be > the person who runs it each and every time? > > > Simon Mac Donald > http://simonmacdonald.com > > On Fri, Sep 22, 2017 at 6:00 PM, julio cesar sanchez < > jcesarmob...@gmail.com > > wrote: > > > For next release I want cordova-plugin-statusbar as I fixed it to work > > properly on iPhone X > > > > 2017-09-22 21:27 GMT+02:00 Steven Gill : > > > > > Please review the blog post for the release > > > > > > https://github.com/apache/cordova-docs/pull/734 > > > > > > On Wed, Sep 20, 2017 at 4:38 PM, Steven Gill > > > wrote: > > > > > > > Yeah I only released the plugins that people mentioned in this thread > > to > > > > release. I can fire up another plugins release next week. What > plugins > > do > > > > people want reviewed/released? > > > > > > > > On Wed, Sep 20, 2017 at 4:36 PM, Simon MacDonald < > > > > simon.macdon...@gmail.com> wrote: > > > > > > > >> Just realized that cordova-plugin-file-transfer was never bumped. It > > > >> includes an important fix for apps. Without it new apps may be > > rejected > > > >> from the Play Store. > > > >> > > > >> > > > >> Simon Mac Donald > > > >> http://simonmacdonald.com > > > >> > > > >> On Wed, Sep 20, 2017 at 1:33 PM, Steven Gill < > stevengil...@gmail.com> > > > >> wrote: > > > >> > > > >> > the ios release blog post tells users about the console plugin. > > > >> > http://cordova.apache.org/announcements/2017/09/08/ios- > release.html > > > >> > > > > >> > I'll make sure to highlight these changes in the plugins release > > blog > > > >> post. > > > >> > > > > >> > Starting a new vote with console + compat only having minor bumps > > > >> > > > > >> > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < > > > >> > jcesarmob...@gmail.com > > > >> > > wrote: > > > >> > > > > >> > > There has been already a few people asking about the duplicate > > > >> symbols on > > > >> > > slack > > > >> > > > > > >> > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald < > > > simon.macdon...@gmail.com > > > >> >: > > > >> > > > > > >> > > > IMHO both cordova-plugin-compat and cordova-plugin-console > > should > > > >> > receive > > > >> > > > minor version bumps. Neither breaks backwards compatibility > so I > > > >> don't > > > >> > > feel > > > >> > > > like a major version bump is warranted. > > > >> > > > > > > >> > > > As well all of our core plugins that depend on > > > cordova-plugin-compat > > > >> > use > > > >> > > > the ^1.x in their semver so they would pull in the earlier > > version > > > >> of > > > >> > the > > > >> > > > compat plugin and in combination with the upcoming > > cordova-android > > > >> > 6.3.0 > > > >> > > > pretty much all apps will fail to build. > > > >> > > > > > > >> > > > When it comes to cordova-plugin-console we should also err on > > the > > > >> side > > > >> > of > > > >> > > > caution when it comes to the version number bump. I spent some > > > time > > > >> > this > > > >> > > > morning debugging an internal app that was using cordova-ios > > 4.5.0 > > > >> and > > > >> > > > cordova-plugin-console. It was failing to build because of > > > duplicate > > > >> > > code. > > > >> > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release > > > before > > > >> > > > cordova-ios 4.5.0 the problem would not have existed. > > > >> > > > > > > >> > > > I think we need to be ready to start answering that question > as > > to > > > >> why > > > >> > > apps > > > >> > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post > > is > > > in > > > >> > > order? > > > >> > > > > > > >> > > > My recommendations is to restart this vote thread with the > four > > > >> plugins > > > >> > > but > > > >> > > > tag their versions as cordova-plugin-compat@1.2.0, > > > >> > > > cordova-plugin-console@1.1.0. The device motion and device > > > >> orientation > > > >> > > > plugins can have any version number we want as they will not > run > > > >> into > > > >> > the > > > >> > > > above problems. > > > >> > > > > > > >> > > > > > > >> > > > Simon Mac Donald > > > >> > > > http://simonmacdonald.com > > > >> > > > > > > >> > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill < > > > >> stevengil...@gmail.com> > > > >> > > > wrote: > > > >> > > > > > > >> > > > > Plugin vote is going to fail it seems due to the issue simon > > > >> found. > > > >> > > > > > > > >> > > > > Simons message: > > > >> > > > > "Failed > > > >> > > > > * Added cordova-plugin-camera to a project
Re: [DISCUSS] Plugin release
Thanks, trying get back into being more involved on the cordova side. Simon Mac Donald http://simonmacdonald.com On Fri, Sep 22, 2017 at 6:06 PM, julio cesar sanchezwrote: > Yes, it's documented in coho > https://github.com/apache/cordova-coho/blob/master/docs/ > plugins-release-process.md > > 2017-09-23 0:04 GMT+02:00 Simon MacDonald : > > > Yeah, we should be doing another plugins release soon. We have: > > > > cordova-plugin-status-bar > > cordova-plugin-file-transfer > > > > Needing releases. > > > > Steve, is the release process documented anywhere so you don't have to be > > the person who runs it each and every time? > > > > > > Simon Mac Donald > > http://simonmacdonald.com > > > > On Fri, Sep 22, 2017 at 6:00 PM, julio cesar sanchez < > > jcesarmob...@gmail.com > > > wrote: > > > > > For next release I want cordova-plugin-statusbar as I fixed it to work > > > properly on iPhone X > > > > > > 2017-09-22 21:27 GMT+02:00 Steven Gill : > > > > > > > Please review the blog post for the release > > > > > > > > https://github.com/apache/cordova-docs/pull/734 > > > > > > > > On Wed, Sep 20, 2017 at 4:38 PM, Steven Gill > > > > > wrote: > > > > > > > > > Yeah I only released the plugins that people mentioned in this > thread > > > to > > > > > release. I can fire up another plugins release next week. What > > plugins > > > do > > > > > people want reviewed/released? > > > > > > > > > > On Wed, Sep 20, 2017 at 4:36 PM, Simon MacDonald < > > > > > simon.macdon...@gmail.com> wrote: > > > > > > > > > >> Just realized that cordova-plugin-file-transfer was never bumped. > It > > > > >> includes an important fix for apps. Without it new apps may be > > > rejected > > > > >> from the Play Store. > > > > >> > > > > >> > > > > >> Simon Mac Donald > > > > >> http://simonmacdonald.com > > > > >> > > > > >> On Wed, Sep 20, 2017 at 1:33 PM, Steven Gill < > > stevengil...@gmail.com> > > > > >> wrote: > > > > >> > > > > >> > the ios release blog post tells users about the console plugin. > > > > >> > http://cordova.apache.org/announcements/2017/09/08/ios- > > release.html > > > > >> > > > > > >> > I'll make sure to highlight these changes in the plugins release > > > blog > > > > >> post. > > > > >> > > > > > >> > Starting a new vote with console + compat only having minor > bumps > > > > >> > > > > > >> > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < > > > > >> > jcesarmob...@gmail.com > > > > >> > > wrote: > > > > >> > > > > > >> > > There has been already a few people asking about the duplicate > > > > >> symbols on > > > > >> > > slack > > > > >> > > > > > > >> > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald < > > > > simon.macdon...@gmail.com > > > > >> >: > > > > >> > > > > > > >> > > > IMHO both cordova-plugin-compat and cordova-plugin-console > > > should > > > > >> > receive > > > > >> > > > minor version bumps. Neither breaks backwards compatibility > > so I > > > > >> don't > > > > >> > > feel > > > > >> > > > like a major version bump is warranted. > > > > >> > > > > > > > >> > > > As well all of our core plugins that depend on > > > > cordova-plugin-compat > > > > >> > use > > > > >> > > > the ^1.x in their semver so they would pull in the earlier > > > version > > > > >> of > > > > >> > the > > > > >> > > > compat plugin and in combination with the upcoming > > > cordova-android > > > > >> > 6.3.0 > > > > >> > > > pretty much all apps will fail to build. > > > > >> > > > > > > > >> > > > When it comes to cordova-plugin-console we should also err > on > > > the > > > > >> side > > > > >> > of > > > > >> > > > caution when it comes to the version number bump. I spent > some > > > > time > > > > >> > this > > > > >> > > > morning debugging an internal app that was using cordova-ios > > > 4.5.0 > > > > >> and > > > > >> > > > cordova-plugin-console. It was failing to build because of > > > > duplicate > > > > >> > > code. > > > > >> > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release > > > > before > > > > >> > > > cordova-ios 4.5.0 the problem would not have existed. > > > > >> > > > > > > > >> > > > I think we need to be ready to start answering that question > > as > > > to > > > > >> why > > > > >> > > apps > > > > >> > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog > post > > > is > > > > in > > > > >> > > order? > > > > >> > > > > > > > >> > > > My recommendations is to restart this vote thread with the > > four > > > > >> plugins > > > > >> > > but > > > > >> > > > tag their versions as cordova-plugin-compat@1.2.0, > > > > >> > > > cordova-plugin-console@1.1.0. The device motion and device > > > > >> orientation > > > > >> > > > plugins can have any version number we want as they will not > > run > > > > >> into > > > > >> > the > > > > >> > > > above problems. > > > > >> > > > > > > > >> > > > > > > > >> > > > Simon Mac Donald > > > > >> > > >
Re: [DISCUSS] Plugin release
Yes, it's documented in coho https://github.com/apache/cordova-coho/blob/master/docs/plugins-release-process.md 2017-09-23 0:04 GMT+02:00 Simon MacDonald: > Yeah, we should be doing another plugins release soon. We have: > > cordova-plugin-status-bar > cordova-plugin-file-transfer > > Needing releases. > > Steve, is the release process documented anywhere so you don't have to be > the person who runs it each and every time? > > > Simon Mac Donald > http://simonmacdonald.com > > On Fri, Sep 22, 2017 at 6:00 PM, julio cesar sanchez < > jcesarmob...@gmail.com > > wrote: > > > For next release I want cordova-plugin-statusbar as I fixed it to work > > properly on iPhone X > > > > 2017-09-22 21:27 GMT+02:00 Steven Gill : > > > > > Please review the blog post for the release > > > > > > https://github.com/apache/cordova-docs/pull/734 > > > > > > On Wed, Sep 20, 2017 at 4:38 PM, Steven Gill > > > wrote: > > > > > > > Yeah I only released the plugins that people mentioned in this thread > > to > > > > release. I can fire up another plugins release next week. What > plugins > > do > > > > people want reviewed/released? > > > > > > > > On Wed, Sep 20, 2017 at 4:36 PM, Simon MacDonald < > > > > simon.macdon...@gmail.com> wrote: > > > > > > > >> Just realized that cordova-plugin-file-transfer was never bumped. It > > > >> includes an important fix for apps. Without it new apps may be > > rejected > > > >> from the Play Store. > > > >> > > > >> > > > >> Simon Mac Donald > > > >> http://simonmacdonald.com > > > >> > > > >> On Wed, Sep 20, 2017 at 1:33 PM, Steven Gill < > stevengil...@gmail.com> > > > >> wrote: > > > >> > > > >> > the ios release blog post tells users about the console plugin. > > > >> > http://cordova.apache.org/announcements/2017/09/08/ios- > release.html > > > >> > > > > >> > I'll make sure to highlight these changes in the plugins release > > blog > > > >> post. > > > >> > > > > >> > Starting a new vote with console + compat only having minor bumps > > > >> > > > > >> > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < > > > >> > jcesarmob...@gmail.com > > > >> > > wrote: > > > >> > > > > >> > > There has been already a few people asking about the duplicate > > > >> symbols on > > > >> > > slack > > > >> > > > > > >> > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald < > > > simon.macdon...@gmail.com > > > >> >: > > > >> > > > > > >> > > > IMHO both cordova-plugin-compat and cordova-plugin-console > > should > > > >> > receive > > > >> > > > minor version bumps. Neither breaks backwards compatibility > so I > > > >> don't > > > >> > > feel > > > >> > > > like a major version bump is warranted. > > > >> > > > > > > >> > > > As well all of our core plugins that depend on > > > cordova-plugin-compat > > > >> > use > > > >> > > > the ^1.x in their semver so they would pull in the earlier > > version > > > >> of > > > >> > the > > > >> > > > compat plugin and in combination with the upcoming > > cordova-android > > > >> > 6.3.0 > > > >> > > > pretty much all apps will fail to build. > > > >> > > > > > > >> > > > When it comes to cordova-plugin-console we should also err on > > the > > > >> side > > > >> > of > > > >> > > > caution when it comes to the version number bump. I spent some > > > time > > > >> > this > > > >> > > > morning debugging an internal app that was using cordova-ios > > 4.5.0 > > > >> and > > > >> > > > cordova-plugin-console. It was failing to build because of > > > duplicate > > > >> > > code. > > > >> > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release > > > before > > > >> > > > cordova-ios 4.5.0 the problem would not have existed. > > > >> > > > > > > >> > > > I think we need to be ready to start answering that question > as > > to > > > >> why > > > >> > > apps > > > >> > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post > > is > > > in > > > >> > > order? > > > >> > > > > > > >> > > > My recommendations is to restart this vote thread with the > four > > > >> plugins > > > >> > > but > > > >> > > > tag their versions as cordova-plugin-compat@1.2.0, > > > >> > > > cordova-plugin-console@1.1.0. The device motion and device > > > >> orientation > > > >> > > > plugins can have any version number we want as they will not > run > > > >> into > > > >> > the > > > >> > > > above problems. > > > >> > > > > > > >> > > > > > > >> > > > Simon Mac Donald > > > >> > > > http://simonmacdonald.com > > > >> > > > > > > >> > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill < > > > >> stevengil...@gmail.com> > > > >> > > > wrote: > > > >> > > > > > > >> > > > > Plugin vote is going to fail it seems due to the issue simon > > > >> found. > > > >> > > > > > > > >> > > > > Simons message: > > > >> > > > > "Failed > > > >> > > > > * Added cordova-plugin-camera to a project with > > cordova-android > > > >> 6.3.0 > > > >> > > > which > > > >> > > > > depends on cordova-plugin-compat and the
Re: [DISCUSS] Plugin release
Yeah, we should be doing another plugins release soon. We have: cordova-plugin-status-bar cordova-plugin-file-transfer Needing releases. Steve, is the release process documented anywhere so you don't have to be the person who runs it each and every time? Simon Mac Donald http://simonmacdonald.com On Fri, Sep 22, 2017 at 6:00 PM, julio cesar sanchezwrote: > For next release I want cordova-plugin-statusbar as I fixed it to work > properly on iPhone X > > 2017-09-22 21:27 GMT+02:00 Steven Gill : > > > Please review the blog post for the release > > > > https://github.com/apache/cordova-docs/pull/734 > > > > On Wed, Sep 20, 2017 at 4:38 PM, Steven Gill > > wrote: > > > > > Yeah I only released the plugins that people mentioned in this thread > to > > > release. I can fire up another plugins release next week. What plugins > do > > > people want reviewed/released? > > > > > > On Wed, Sep 20, 2017 at 4:36 PM, Simon MacDonald < > > > simon.macdon...@gmail.com> wrote: > > > > > >> Just realized that cordova-plugin-file-transfer was never bumped. It > > >> includes an important fix for apps. Without it new apps may be > rejected > > >> from the Play Store. > > >> > > >> > > >> Simon Mac Donald > > >> http://simonmacdonald.com > > >> > > >> On Wed, Sep 20, 2017 at 1:33 PM, Steven Gill > > >> wrote: > > >> > > >> > the ios release blog post tells users about the console plugin. > > >> > http://cordova.apache.org/announcements/2017/09/08/ios-release.html > > >> > > > >> > I'll make sure to highlight these changes in the plugins release > blog > > >> post. > > >> > > > >> > Starting a new vote with console + compat only having minor bumps > > >> > > > >> > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < > > >> > jcesarmob...@gmail.com > > >> > > wrote: > > >> > > > >> > > There has been already a few people asking about the duplicate > > >> symbols on > > >> > > slack > > >> > > > > >> > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald < > > simon.macdon...@gmail.com > > >> >: > > >> > > > > >> > > > IMHO both cordova-plugin-compat and cordova-plugin-console > should > > >> > receive > > >> > > > minor version bumps. Neither breaks backwards compatibility so I > > >> don't > > >> > > feel > > >> > > > like a major version bump is warranted. > > >> > > > > > >> > > > As well all of our core plugins that depend on > > cordova-plugin-compat > > >> > use > > >> > > > the ^1.x in their semver so they would pull in the earlier > version > > >> of > > >> > the > > >> > > > compat plugin and in combination with the upcoming > cordova-android > > >> > 6.3.0 > > >> > > > pretty much all apps will fail to build. > > >> > > > > > >> > > > When it comes to cordova-plugin-console we should also err on > the > > >> side > > >> > of > > >> > > > caution when it comes to the version number bump. I spent some > > time > > >> > this > > >> > > > morning debugging an internal app that was using cordova-ios > 4.5.0 > > >> and > > >> > > > cordova-plugin-console. It was failing to build because of > > duplicate > > >> > > code. > > >> > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release > > before > > >> > > > cordova-ios 4.5.0 the problem would not have existed. > > >> > > > > > >> > > > I think we need to be ready to start answering that question as > to > > >> why > > >> > > apps > > >> > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post > is > > in > > >> > > order? > > >> > > > > > >> > > > My recommendations is to restart this vote thread with the four > > >> plugins > > >> > > but > > >> > > > tag their versions as cordova-plugin-compat@1.2.0, > > >> > > > cordova-plugin-console@1.1.0. The device motion and device > > >> orientation > > >> > > > plugins can have any version number we want as they will not run > > >> into > > >> > the > > >> > > > above problems. > > >> > > > > > >> > > > > > >> > > > Simon Mac Donald > > >> > > > http://simonmacdonald.com > > >> > > > > > >> > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill < > > >> stevengil...@gmail.com> > > >> > > > wrote: > > >> > > > > > >> > > > > Plugin vote is going to fail it seems due to the issue simon > > >> found. > > >> > > > > > > >> > > > > Simons message: > > >> > > > > "Failed > > >> > > > > * Added cordova-plugin-camera to a project with > cordova-android > > >> 6.3.0 > > >> > > > which > > >> > > > > depends on cordova-plugin-compat and the build fails. > > >> > > > > > > >> > > > > The reason the build fails is that all of the cordova plugins > > that > > >> > > depend > > >> > > > > on cordova-plugin-compat do so using a semver of ^1.0.0 or > > ^1.1.0. > > >> > > Since > > >> > > > > compat was bumped to 2.0.0 when you install > > cordova-plugin-camera > > >> on > > >> > > your > > >> > > > > cordova-android 6.3.0 project it fails the semver and it pulls > > in > > >> the > > >> > > > 1.1.0 > > >> > > > > version. Now
Re: [DISCUSS] Plugin release
For next release I want cordova-plugin-statusbar as I fixed it to work properly on iPhone X 2017-09-22 21:27 GMT+02:00 Steven Gill: > Please review the blog post for the release > > https://github.com/apache/cordova-docs/pull/734 > > On Wed, Sep 20, 2017 at 4:38 PM, Steven Gill > wrote: > > > Yeah I only released the plugins that people mentioned in this thread to > > release. I can fire up another plugins release next week. What plugins do > > people want reviewed/released? > > > > On Wed, Sep 20, 2017 at 4:36 PM, Simon MacDonald < > > simon.macdon...@gmail.com> wrote: > > > >> Just realized that cordova-plugin-file-transfer was never bumped. It > >> includes an important fix for apps. Without it new apps may be rejected > >> from the Play Store. > >> > >> > >> Simon Mac Donald > >> http://simonmacdonald.com > >> > >> On Wed, Sep 20, 2017 at 1:33 PM, Steven Gill > >> wrote: > >> > >> > the ios release blog post tells users about the console plugin. > >> > http://cordova.apache.org/announcements/2017/09/08/ios-release.html > >> > > >> > I'll make sure to highlight these changes in the plugins release blog > >> post. > >> > > >> > Starting a new vote with console + compat only having minor bumps > >> > > >> > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < > >> > jcesarmob...@gmail.com > >> > > wrote: > >> > > >> > > There has been already a few people asking about the duplicate > >> symbols on > >> > > slack > >> > > > >> > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald < > simon.macdon...@gmail.com > >> >: > >> > > > >> > > > IMHO both cordova-plugin-compat and cordova-plugin-console should > >> > receive > >> > > > minor version bumps. Neither breaks backwards compatibility so I > >> don't > >> > > feel > >> > > > like a major version bump is warranted. > >> > > > > >> > > > As well all of our core plugins that depend on > cordova-plugin-compat > >> > use > >> > > > the ^1.x in their semver so they would pull in the earlier version > >> of > >> > the > >> > > > compat plugin and in combination with the upcoming cordova-android > >> > 6.3.0 > >> > > > pretty much all apps will fail to build. > >> > > > > >> > > > When it comes to cordova-plugin-console we should also err on the > >> side > >> > of > >> > > > caution when it comes to the version number bump. I spent some > time > >> > this > >> > > > morning debugging an internal app that was using cordova-ios 4.5.0 > >> and > >> > > > cordova-plugin-console. It was failing to build because of > duplicate > >> > > code. > >> > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release > before > >> > > > cordova-ios 4.5.0 the problem would not have existed. > >> > > > > >> > > > I think we need to be ready to start answering that question as to > >> why > >> > > apps > >> > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post is > in > >> > > order? > >> > > > > >> > > > My recommendations is to restart this vote thread with the four > >> plugins > >> > > but > >> > > > tag their versions as cordova-plugin-compat@1.2.0, > >> > > > cordova-plugin-console@1.1.0. The device motion and device > >> orientation > >> > > > plugins can have any version number we want as they will not run > >> into > >> > the > >> > > > above problems. > >> > > > > >> > > > > >> > > > Simon Mac Donald > >> > > > http://simonmacdonald.com > >> > > > > >> > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill < > >> stevengil...@gmail.com> > >> > > > wrote: > >> > > > > >> > > > > Plugin vote is going to fail it seems due to the issue simon > >> found. > >> > > > > > >> > > > > Simons message: > >> > > > > "Failed > >> > > > > * Added cordova-plugin-camera to a project with cordova-android > >> 6.3.0 > >> > > > which > >> > > > > depends on cordova-plugin-compat and the build fails. > >> > > > > > >> > > > > The reason the build fails is that all of the cordova plugins > that > >> > > depend > >> > > > > on cordova-plugin-compat do so using a semver of ^1.0.0 or > ^1.1.0. > >> > > Since > >> > > > > compat was bumped to 2.0.0 when you install > cordova-plugin-camera > >> on > >> > > your > >> > > > > cordova-android 6.3.0 project it fails the semver and it pulls > in > >> the > >> > > > 1.1.0 > >> > > > > version. Now both compat and cordova-android deliver the same > >> classes > >> > > and > >> > > > > the build fails." > >> > > > > > >> > > > > I actually have 1.2.0 version of the plugin already tagged from > >> when > >> > I > >> > > > ran > >> > > > > the plugin process on Monday. It is identical to the 2.0.0 > version > >> > that > >> > > > is > >> > > > > being voted on. We can either stop the current vote thread and > >> start > >> > a > >> > > > new > >> > > > > one with 1.2.0 instead of 2.0.0, or we could continue the > current > >> > vote > >> > > > > thread and start a new one just for compat@1.2.0. If we go with > >> > option > >> > > > 2, > >> > > > > we can release both
Re: [DISCUSS] Plugin release
Please review the blog post for the release https://github.com/apache/cordova-docs/pull/734 On Wed, Sep 20, 2017 at 4:38 PM, Steven Gillwrote: > Yeah I only released the plugins that people mentioned in this thread to > release. I can fire up another plugins release next week. What plugins do > people want reviewed/released? > > On Wed, Sep 20, 2017 at 4:36 PM, Simon MacDonald < > simon.macdon...@gmail.com> wrote: > >> Just realized that cordova-plugin-file-transfer was never bumped. It >> includes an important fix for apps. Without it new apps may be rejected >> from the Play Store. >> >> >> Simon Mac Donald >> http://simonmacdonald.com >> >> On Wed, Sep 20, 2017 at 1:33 PM, Steven Gill >> wrote: >> >> > the ios release blog post tells users about the console plugin. >> > http://cordova.apache.org/announcements/2017/09/08/ios-release.html >> > >> > I'll make sure to highlight these changes in the plugins release blog >> post. >> > >> > Starting a new vote with console + compat only having minor bumps >> > >> > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < >> > jcesarmob...@gmail.com >> > > wrote: >> > >> > > There has been already a few people asking about the duplicate >> symbols on >> > > slack >> > > >> > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald > >: >> > > >> > > > IMHO both cordova-plugin-compat and cordova-plugin-console should >> > receive >> > > > minor version bumps. Neither breaks backwards compatibility so I >> don't >> > > feel >> > > > like a major version bump is warranted. >> > > > >> > > > As well all of our core plugins that depend on cordova-plugin-compat >> > use >> > > > the ^1.x in their semver so they would pull in the earlier version >> of >> > the >> > > > compat plugin and in combination with the upcoming cordova-android >> > 6.3.0 >> > > > pretty much all apps will fail to build. >> > > > >> > > > When it comes to cordova-plugin-console we should also err on the >> side >> > of >> > > > caution when it comes to the version number bump. I spent some time >> > this >> > > > morning debugging an internal app that was using cordova-ios 4.5.0 >> and >> > > > cordova-plugin-console. It was failing to build because of duplicate >> > > code. >> > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release before >> > > > cordova-ios 4.5.0 the problem would not have existed. >> > > > >> > > > I think we need to be ready to start answering that question as to >> why >> > > apps >> > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post is in >> > > order? >> > > > >> > > > My recommendations is to restart this vote thread with the four >> plugins >> > > but >> > > > tag their versions as cordova-plugin-compat@1.2.0, >> > > > cordova-plugin-console@1.1.0. The device motion and device >> orientation >> > > > plugins can have any version number we want as they will not run >> into >> > the >> > > > above problems. >> > > > >> > > > >> > > > Simon Mac Donald >> > > > http://simonmacdonald.com >> > > > >> > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill < >> stevengil...@gmail.com> >> > > > wrote: >> > > > >> > > > > Plugin vote is going to fail it seems due to the issue simon >> found. >> > > > > >> > > > > Simons message: >> > > > > "Failed >> > > > > * Added cordova-plugin-camera to a project with cordova-android >> 6.3.0 >> > > > which >> > > > > depends on cordova-plugin-compat and the build fails. >> > > > > >> > > > > The reason the build fails is that all of the cordova plugins that >> > > depend >> > > > > on cordova-plugin-compat do so using a semver of ^1.0.0 or ^1.1.0. >> > > Since >> > > > > compat was bumped to 2.0.0 when you install cordova-plugin-camera >> on >> > > your >> > > > > cordova-android 6.3.0 project it fails the semver and it pulls in >> the >> > > > 1.1.0 >> > > > > version. Now both compat and cordova-android deliver the same >> classes >> > > and >> > > > > the build fails." >> > > > > >> > > > > I actually have 1.2.0 version of the plugin already tagged from >> when >> > I >> > > > ran >> > > > > the plugin process on Monday. It is identical to the 2.0.0 version >> > that >> > > > is >> > > > > being voted on. We can either stop the current vote thread and >> start >> > a >> > > > new >> > > > > one with 1.2.0 instead of 2.0.0, or we could continue the current >> > vote >> > > > > thread and start a new one just for compat@1.2.0. If we go with >> > option >> > > > 2, >> > > > > we can release both 1.2.0 and 2.0.0. >> > > > > >> > > > > This is a good point to remember in the future. Deprecation >> should be >> > > > minor >> > > > > not major bumps. >> > > > > >> > > > > >> > > > > On Tue, Sep 12, 2017 at 11:43 PM, Shazron >> wrote: >> > > > > >> > > > > > Created PR for CB-13170 cordova-plugin-console >> > > > > > https://github.com/apache/cordova-plugin-console/pull/25 >> > > > > > >> > > > > > On Tue, Sep 12, 2017 at 7:20 AM,
Re: [DISCUSS] Plugin release
Yeah I only released the plugins that people mentioned in this thread to release. I can fire up another plugins release next week. What plugins do people want reviewed/released? On Wed, Sep 20, 2017 at 4:36 PM, Simon MacDonaldwrote: > Just realized that cordova-plugin-file-transfer was never bumped. It > includes an important fix for apps. Without it new apps may be rejected > from the Play Store. > > > Simon Mac Donald > http://simonmacdonald.com > > On Wed, Sep 20, 2017 at 1:33 PM, Steven Gill > wrote: > > > the ios release blog post tells users about the console plugin. > > http://cordova.apache.org/announcements/2017/09/08/ios-release.html > > > > I'll make sure to highlight these changes in the plugins release blog > post. > > > > Starting a new vote with console + compat only having minor bumps > > > > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < > > jcesarmob...@gmail.com > > > wrote: > > > > > There has been already a few people asking about the duplicate symbols > on > > > slack > > > > > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald >: > > > > > > > IMHO both cordova-plugin-compat and cordova-plugin-console should > > receive > > > > minor version bumps. Neither breaks backwards compatibility so I > don't > > > feel > > > > like a major version bump is warranted. > > > > > > > > As well all of our core plugins that depend on cordova-plugin-compat > > use > > > > the ^1.x in their semver so they would pull in the earlier version of > > the > > > > compat plugin and in combination with the upcoming cordova-android > > 6.3.0 > > > > pretty much all apps will fail to build. > > > > > > > > When it comes to cordova-plugin-console we should also err on the > side > > of > > > > caution when it comes to the version number bump. I spent some time > > this > > > > morning debugging an internal app that was using cordova-ios 4.5.0 > and > > > > cordova-plugin-console. It was failing to build because of duplicate > > > code. > > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release before > > > > cordova-ios 4.5.0 the problem would not have existed. > > > > > > > > I think we need to be ready to start answering that question as to > why > > > apps > > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post is in > > > order? > > > > > > > > My recommendations is to restart this vote thread with the four > plugins > > > but > > > > tag their versions as cordova-plugin-compat@1.2.0, > > > > cordova-plugin-console@1.1.0. The device motion and device > orientation > > > > plugins can have any version number we want as they will not run into > > the > > > > above problems. > > > > > > > > > > > > Simon Mac Donald > > > > http://simonmacdonald.com > > > > > > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill > > > > > wrote: > > > > > > > > > Plugin vote is going to fail it seems due to the issue simon found. > > > > > > > > > > Simons message: > > > > > "Failed > > > > > * Added cordova-plugin-camera to a project with cordova-android > 6.3.0 > > > > which > > > > > depends on cordova-plugin-compat and the build fails. > > > > > > > > > > The reason the build fails is that all of the cordova plugins that > > > depend > > > > > on cordova-plugin-compat do so using a semver of ^1.0.0 or ^1.1.0. > > > Since > > > > > compat was bumped to 2.0.0 when you install cordova-plugin-camera > on > > > your > > > > > cordova-android 6.3.0 project it fails the semver and it pulls in > the > > > > 1.1.0 > > > > > version. Now both compat and cordova-android deliver the same > classes > > > and > > > > > the build fails." > > > > > > > > > > I actually have 1.2.0 version of the plugin already tagged from > when > > I > > > > ran > > > > > the plugin process on Monday. It is identical to the 2.0.0 version > > that > > > > is > > > > > being voted on. We can either stop the current vote thread and > start > > a > > > > new > > > > > one with 1.2.0 instead of 2.0.0, or we could continue the current > > vote > > > > > thread and start a new one just for compat@1.2.0. If we go with > > option > > > > 2, > > > > > we can release both 1.2.0 and 2.0.0. > > > > > > > > > > This is a good point to remember in the future. Deprecation should > be > > > > minor > > > > > not major bumps. > > > > > > > > > > > > > > > On Tue, Sep 12, 2017 at 11:43 PM, Shazron > wrote: > > > > > > > > > > > Created PR for CB-13170 cordova-plugin-console > > > > > > https://github.com/apache/cordova-plugin-console/pull/25 > > > > > > > > > > > > On Tue, Sep 12, 2017 at 7:20 AM, Simon MacDonald < > > > > > > simon.macdon...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Both of: > > > > > > > > > > > > > > cordova-plugin-device-motion > > > > > > > cordova-plugin-device-orientation > > > > > > > > > > > > > > should get their deprecation PR's merge and also released. > > > > > > > > > > > > >
Re: [DISCUSS] Plugin release
Just realized that cordova-plugin-file-transfer was never bumped. It includes an important fix for apps. Without it new apps may be rejected from the Play Store. Simon Mac Donald http://simonmacdonald.com On Wed, Sep 20, 2017 at 1:33 PM, Steven Gillwrote: > the ios release blog post tells users about the console plugin. > http://cordova.apache.org/announcements/2017/09/08/ios-release.html > > I'll make sure to highlight these changes in the plugins release blog post. > > Starting a new vote with console + compat only having minor bumps > > On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchez < > jcesarmob...@gmail.com > > wrote: > > > There has been already a few people asking about the duplicate symbols on > > slack > > > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald : > > > > > IMHO both cordova-plugin-compat and cordova-plugin-console should > receive > > > minor version bumps. Neither breaks backwards compatibility so I don't > > feel > > > like a major version bump is warranted. > > > > > > As well all of our core plugins that depend on cordova-plugin-compat > use > > > the ^1.x in their semver so they would pull in the earlier version of > the > > > compat plugin and in combination with the upcoming cordova-android > 6.3.0 > > > pretty much all apps will fail to build. > > > > > > When it comes to cordova-plugin-console we should also err on the side > of > > > caution when it comes to the version number bump. I spent some time > this > > > morning debugging an internal app that was using cordova-ios 4.5.0 and > > > cordova-plugin-console. It was failing to build because of duplicate > > code. > > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release before > > > cordova-ios 4.5.0 the problem would not have existed. > > > > > > I think we need to be ready to start answering that question as to why > > apps > > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post is in > > order? > > > > > > My recommendations is to restart this vote thread with the four plugins > > but > > > tag their versions as cordova-plugin-compat@1.2.0, > > > cordova-plugin-console@1.1.0. The device motion and device orientation > > > plugins can have any version number we want as they will not run into > the > > > above problems. > > > > > > > > > Simon Mac Donald > > > http://simonmacdonald.com > > > > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill > > > wrote: > > > > > > > Plugin vote is going to fail it seems due to the issue simon found. > > > > > > > > Simons message: > > > > "Failed > > > > * Added cordova-plugin-camera to a project with cordova-android 6.3.0 > > > which > > > > depends on cordova-plugin-compat and the build fails. > > > > > > > > The reason the build fails is that all of the cordova plugins that > > depend > > > > on cordova-plugin-compat do so using a semver of ^1.0.0 or ^1.1.0. > > Since > > > > compat was bumped to 2.0.0 when you install cordova-plugin-camera on > > your > > > > cordova-android 6.3.0 project it fails the semver and it pulls in the > > > 1.1.0 > > > > version. Now both compat and cordova-android deliver the same classes > > and > > > > the build fails." > > > > > > > > I actually have 1.2.0 version of the plugin already tagged from when > I > > > ran > > > > the plugin process on Monday. It is identical to the 2.0.0 version > that > > > is > > > > being voted on. We can either stop the current vote thread and start > a > > > new > > > > one with 1.2.0 instead of 2.0.0, or we could continue the current > vote > > > > thread and start a new one just for compat@1.2.0. If we go with > option > > > 2, > > > > we can release both 1.2.0 and 2.0.0. > > > > > > > > This is a good point to remember in the future. Deprecation should be > > > minor > > > > not major bumps. > > > > > > > > > > > > On Tue, Sep 12, 2017 at 11:43 PM, Shazron wrote: > > > > > > > > > Created PR for CB-13170 cordova-plugin-console > > > > > https://github.com/apache/cordova-plugin-console/pull/25 > > > > > > > > > > On Tue, Sep 12, 2017 at 7:20 AM, Simon MacDonald < > > > > > simon.macdon...@gmail.com> > > > > > wrote: > > > > > > > > > > > Both of: > > > > > > > > > > > > cordova-plugin-device-motion > > > > > > cordova-plugin-device-orientation > > > > > > > > > > > > should get their deprecation PR's merge and also released. > > > > > > > > > > > > Simon Mac Donald > > > > > > http://simonmacdonald.com > > > > > > > > > > > > > > > > > > On Mon, Sep 11, 2017 at 7:03 PM, Shazron > > wrote: > > > > > > > +1 on console. No PRs for that yet though so it's not ready. > > > > > > > > > > > > > > On Tue, Sep 12, 2017 at 5:46 AM, Steven Gill < > > > stevengil...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > > > >> Console should be released too since it has been moved back > into > > > ios > > > > > for > > > > > > >> next release.
Re: [DISCUSS] Plugin release
the ios release blog post tells users about the console plugin. http://cordova.apache.org/announcements/2017/09/08/ios-release.html I'll make sure to highlight these changes in the plugins release blog post. Starting a new vote with console + compat only having minor bumps On Wed, Sep 20, 2017 at 8:16 AM, julio cesar sanchezwrote: > There has been already a few people asking about the duplicate symbols on > slack > > 2017-09-20 17:06 GMT+02:00 Simon MacDonald : > > > IMHO both cordova-plugin-compat and cordova-plugin-console should receive > > minor version bumps. Neither breaks backwards compatibility so I don't > feel > > like a major version bump is warranted. > > > > As well all of our core plugins that depend on cordova-plugin-compat use > > the ^1.x in their semver so they would pull in the earlier version of the > > compat plugin and in combination with the upcoming cordova-android 6.3.0 > > pretty much all apps will fail to build. > > > > When it comes to cordova-plugin-console we should also err on the side of > > caution when it comes to the version number bump. I spent some time this > > morning debugging an internal app that was using cordova-ios 4.5.0 and > > cordova-plugin-console. It was failing to build because of duplicate > code. > > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release before > > cordova-ios 4.5.0 the problem would not have existed. > > > > I think we need to be ready to start answering that question as to why > apps > > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post is in > order? > > > > My recommendations is to restart this vote thread with the four plugins > but > > tag their versions as cordova-plugin-compat@1.2.0, > > cordova-plugin-console@1.1.0. The device motion and device orientation > > plugins can have any version number we want as they will not run into the > > above problems. > > > > > > Simon Mac Donald > > http://simonmacdonald.com > > > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill > > wrote: > > > > > Plugin vote is going to fail it seems due to the issue simon found. > > > > > > Simons message: > > > "Failed > > > * Added cordova-plugin-camera to a project with cordova-android 6.3.0 > > which > > > depends on cordova-plugin-compat and the build fails. > > > > > > The reason the build fails is that all of the cordova plugins that > depend > > > on cordova-plugin-compat do so using a semver of ^1.0.0 or ^1.1.0. > Since > > > compat was bumped to 2.0.0 when you install cordova-plugin-camera on > your > > > cordova-android 6.3.0 project it fails the semver and it pulls in the > > 1.1.0 > > > version. Now both compat and cordova-android deliver the same classes > and > > > the build fails." > > > > > > I actually have 1.2.0 version of the plugin already tagged from when I > > ran > > > the plugin process on Monday. It is identical to the 2.0.0 version that > > is > > > being voted on. We can either stop the current vote thread and start a > > new > > > one with 1.2.0 instead of 2.0.0, or we could continue the current vote > > > thread and start a new one just for compat@1.2.0. If we go with option > > 2, > > > we can release both 1.2.0 and 2.0.0. > > > > > > This is a good point to remember in the future. Deprecation should be > > minor > > > not major bumps. > > > > > > > > > On Tue, Sep 12, 2017 at 11:43 PM, Shazron wrote: > > > > > > > Created PR for CB-13170 cordova-plugin-console > > > > https://github.com/apache/cordova-plugin-console/pull/25 > > > > > > > > On Tue, Sep 12, 2017 at 7:20 AM, Simon MacDonald < > > > > simon.macdon...@gmail.com> > > > > wrote: > > > > > > > > > Both of: > > > > > > > > > > cordova-plugin-device-motion > > > > > cordova-plugin-device-orientation > > > > > > > > > > should get their deprecation PR's merge and also released. > > > > > > > > > > Simon Mac Donald > > > > > http://simonmacdonald.com > > > > > > > > > > > > > > > On Mon, Sep 11, 2017 at 7:03 PM, Shazron > wrote: > > > > > > +1 on console. No PRs for that yet though so it's not ready. > > > > > > > > > > > > On Tue, Sep 12, 2017 at 5:46 AM, Steven Gill < > > stevengil...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > >> Console should be released too since it has been moved back into > > ios > > > > for > > > > > >> next release. https://issues.apache.org/jira/browse/CB-13170 > > > > > >> > > > > > >> On Sep 11, 2017 2:04 PM, "Jesse" > wrote: > > > > > >> > > > > > >> > Android release is dependent on us releasing an > > > > > >> > updated cordova-plugin-compat > > > > > >> > > > > > > >> > Anyone have any reasons to not do a release? Anything > > outstanding > > > > > >> > anyone wants to get merged in before moving ahead with a > plugins > > > > > >> > release? Any other comments on the topic? > > > > > >> > > > > > > >> > Cheers, > > > > > >> > Jesse > > > > > >> > > > > > >
Re: [DISCUSS] Plugin release
There has been already a few people asking about the duplicate symbols on slack 2017-09-20 17:06 GMT+02:00 Simon MacDonald: > IMHO both cordova-plugin-compat and cordova-plugin-console should receive > minor version bumps. Neither breaks backwards compatibility so I don't feel > like a major version bump is warranted. > > As well all of our core plugins that depend on cordova-plugin-compat use > the ^1.x in their semver so they would pull in the earlier version of the > compat plugin and in combination with the upcoming cordova-android 6.3.0 > pretty much all apps will fail to build. > > When it comes to cordova-plugin-console we should also err on the side of > caution when it comes to the version number bump. I spent some time this > morning debugging an internal app that was using cordova-ios 4.5.0 and > cordova-plugin-console. It was failing to build because of duplicate code. > If cordova-plugin-console 1.1.0 (not 2.0.0) has been release before > cordova-ios 4.5.0 the problem would not have existed. > > I think we need to be ready to start answering that question as to why apps > using cordova-ios 4.5.0 don't build. Perhaps a quick blog post is in order? > > My recommendations is to restart this vote thread with the four plugins but > tag their versions as cordova-plugin-compat@1.2.0, > cordova-plugin-console@1.1.0. The device motion and device orientation > plugins can have any version number we want as they will not run into the > above problems. > > > Simon Mac Donald > http://simonmacdonald.com > > On Wed, Sep 20, 2017 at 1:44 AM, Steven Gill > wrote: > > > Plugin vote is going to fail it seems due to the issue simon found. > > > > Simons message: > > "Failed > > * Added cordova-plugin-camera to a project with cordova-android 6.3.0 > which > > depends on cordova-plugin-compat and the build fails. > > > > The reason the build fails is that all of the cordova plugins that depend > > on cordova-plugin-compat do so using a semver of ^1.0.0 or ^1.1.0. Since > > compat was bumped to 2.0.0 when you install cordova-plugin-camera on your > > cordova-android 6.3.0 project it fails the semver and it pulls in the > 1.1.0 > > version. Now both compat and cordova-android deliver the same classes and > > the build fails." > > > > I actually have 1.2.0 version of the plugin already tagged from when I > ran > > the plugin process on Monday. It is identical to the 2.0.0 version that > is > > being voted on. We can either stop the current vote thread and start a > new > > one with 1.2.0 instead of 2.0.0, or we could continue the current vote > > thread and start a new one just for compat@1.2.0. If we go with option > 2, > > we can release both 1.2.0 and 2.0.0. > > > > This is a good point to remember in the future. Deprecation should be > minor > > not major bumps. > > > > > > On Tue, Sep 12, 2017 at 11:43 PM, Shazron wrote: > > > > > Created PR for CB-13170 cordova-plugin-console > > > https://github.com/apache/cordova-plugin-console/pull/25 > > > > > > On Tue, Sep 12, 2017 at 7:20 AM, Simon MacDonald < > > > simon.macdon...@gmail.com> > > > wrote: > > > > > > > Both of: > > > > > > > > cordova-plugin-device-motion > > > > cordova-plugin-device-orientation > > > > > > > > should get their deprecation PR's merge and also released. > > > > > > > > Simon Mac Donald > > > > http://simonmacdonald.com > > > > > > > > > > > > On Mon, Sep 11, 2017 at 7:03 PM, Shazron wrote: > > > > > +1 on console. No PRs for that yet though so it's not ready. > > > > > > > > > > On Tue, Sep 12, 2017 at 5:46 AM, Steven Gill < > stevengil...@gmail.com > > > > > > > wrote: > > > > > > > > > >> Console should be released too since it has been moved back into > ios > > > for > > > > >> next release. https://issues.apache.org/jira/browse/CB-13170 > > > > >> > > > > >> On Sep 11, 2017 2:04 PM, "Jesse" wrote: > > > > >> > > > > >> > Android release is dependent on us releasing an > > > > >> > updated cordova-plugin-compat > > > > >> > > > > > >> > Anyone have any reasons to not do a release? Anything > outstanding > > > > >> > anyone wants to get merged in before moving ahead with a plugins > > > > >> > release? Any other comments on the topic? > > > > >> > > > > > >> > Cheers, > > > > >> > Jesse > > > > >> > > > > > >> > > > > > >> > @purplecabbage > > > > >> > risingj.com > > > > >> > > > > > >> > > > > > > > > > - > > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > > > >
Re: [DISCUSS] Plugin release
IMHO both cordova-plugin-compat and cordova-plugin-console should receive minor version bumps. Neither breaks backwards compatibility so I don't feel like a major version bump is warranted. As well all of our core plugins that depend on cordova-plugin-compat use the ^1.x in their semver so they would pull in the earlier version of the compat plugin and in combination with the upcoming cordova-android 6.3.0 pretty much all apps will fail to build. When it comes to cordova-plugin-console we should also err on the side of caution when it comes to the version number bump. I spent some time this morning debugging an internal app that was using cordova-ios 4.5.0 and cordova-plugin-console. It was failing to build because of duplicate code. If cordova-plugin-console 1.1.0 (not 2.0.0) has been release before cordova-ios 4.5.0 the problem would not have existed. I think we need to be ready to start answering that question as to why apps using cordova-ios 4.5.0 don't build. Perhaps a quick blog post is in order? My recommendations is to restart this vote thread with the four plugins but tag their versions as cordova-plugin-compat@1.2.0, cordova-plugin-console@1.1.0. The device motion and device orientation plugins can have any version number we want as they will not run into the above problems. Simon Mac Donald http://simonmacdonald.com On Wed, Sep 20, 2017 at 1:44 AM, Steven Gillwrote: > Plugin vote is going to fail it seems due to the issue simon found. > > Simons message: > "Failed > * Added cordova-plugin-camera to a project with cordova-android 6.3.0 which > depends on cordova-plugin-compat and the build fails. > > The reason the build fails is that all of the cordova plugins that depend > on cordova-plugin-compat do so using a semver of ^1.0.0 or ^1.1.0. Since > compat was bumped to 2.0.0 when you install cordova-plugin-camera on your > cordova-android 6.3.0 project it fails the semver and it pulls in the 1.1.0 > version. Now both compat and cordova-android deliver the same classes and > the build fails." > > I actually have 1.2.0 version of the plugin already tagged from when I ran > the plugin process on Monday. It is identical to the 2.0.0 version that is > being voted on. We can either stop the current vote thread and start a new > one with 1.2.0 instead of 2.0.0, or we could continue the current vote > thread and start a new one just for compat@1.2.0. If we go with option 2, > we can release both 1.2.0 and 2.0.0. > > This is a good point to remember in the future. Deprecation should be minor > not major bumps. > > > On Tue, Sep 12, 2017 at 11:43 PM, Shazron wrote: > > > Created PR for CB-13170 cordova-plugin-console > > https://github.com/apache/cordova-plugin-console/pull/25 > > > > On Tue, Sep 12, 2017 at 7:20 AM, Simon MacDonald < > > simon.macdon...@gmail.com> > > wrote: > > > > > Both of: > > > > > > cordova-plugin-device-motion > > > cordova-plugin-device-orientation > > > > > > should get their deprecation PR's merge and also released. > > > > > > Simon Mac Donald > > > http://simonmacdonald.com > > > > > > > > > On Mon, Sep 11, 2017 at 7:03 PM, Shazron wrote: > > > > +1 on console. No PRs for that yet though so it's not ready. > > > > > > > > On Tue, Sep 12, 2017 at 5:46 AM, Steven Gill > > > > wrote: > > > > > > > >> Console should be released too since it has been moved back into ios > > for > > > >> next release. https://issues.apache.org/jira/browse/CB-13170 > > > >> > > > >> On Sep 11, 2017 2:04 PM, "Jesse" wrote: > > > >> > > > >> > Android release is dependent on us releasing an > > > >> > updated cordova-plugin-compat > > > >> > > > > >> > Anyone have any reasons to not do a release? Anything outstanding > > > >> > anyone wants to get merged in before moving ahead with a plugins > > > >> > release? Any other comments on the topic? > > > >> > > > > >> > Cheers, > > > >> > Jesse > > > >> > > > > >> > > > > >> > @purplecabbage > > > >> > risingj.com > > > >> > > > > >> > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > >
Re: [DISCUSS] Plugin release
Plugin vote is going to fail it seems due to the issue simon found. Simons message: "Failed * Added cordova-plugin-camera to a project with cordova-android 6.3.0 which depends on cordova-plugin-compat and the build fails. The reason the build fails is that all of the cordova plugins that depend on cordova-plugin-compat do so using a semver of ^1.0.0 or ^1.1.0. Since compat was bumped to 2.0.0 when you install cordova-plugin-camera on your cordova-android 6.3.0 project it fails the semver and it pulls in the 1.1.0 version. Now both compat and cordova-android deliver the same classes and the build fails." I actually have 1.2.0 version of the plugin already tagged from when I ran the plugin process on Monday. It is identical to the 2.0.0 version that is being voted on. We can either stop the current vote thread and start a new one with 1.2.0 instead of 2.0.0, or we could continue the current vote thread and start a new one just for compat@1.2.0. If we go with option 2, we can release both 1.2.0 and 2.0.0. This is a good point to remember in the future. Deprecation should be minor not major bumps. On Tue, Sep 12, 2017 at 11:43 PM, Shazronwrote: > Created PR for CB-13170 cordova-plugin-console > https://github.com/apache/cordova-plugin-console/pull/25 > > On Tue, Sep 12, 2017 at 7:20 AM, Simon MacDonald < > simon.macdon...@gmail.com> > wrote: > > > Both of: > > > > cordova-plugin-device-motion > > cordova-plugin-device-orientation > > > > should get their deprecation PR's merge and also released. > > > > Simon Mac Donald > > http://simonmacdonald.com > > > > > > On Mon, Sep 11, 2017 at 7:03 PM, Shazron wrote: > > > +1 on console. No PRs for that yet though so it's not ready. > > > > > > On Tue, Sep 12, 2017 at 5:46 AM, Steven Gill > > wrote: > > > > > >> Console should be released too since it has been moved back into ios > for > > >> next release. https://issues.apache.org/jira/browse/CB-13170 > > >> > > >> On Sep 11, 2017 2:04 PM, "Jesse" wrote: > > >> > > >> > Android release is dependent on us releasing an > > >> > updated cordova-plugin-compat > > >> > > > >> > Anyone have any reasons to not do a release? Anything outstanding > > >> > anyone wants to get merged in before moving ahead with a plugins > > >> > release? Any other comments on the topic? > > >> > > > >> > Cheers, > > >> > Jesse > > >> > > > >> > > > >> > @purplecabbage > > >> > risingj.com > > >> > > > >> > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > >
Re: [DISCUSS] Plugin release
Created PR for CB-13170 cordova-plugin-console https://github.com/apache/cordova-plugin-console/pull/25 On Tue, Sep 12, 2017 at 7:20 AM, Simon MacDonaldwrote: > Both of: > > cordova-plugin-device-motion > cordova-plugin-device-orientation > > should get their deprecation PR's merge and also released. > > Simon Mac Donald > http://simonmacdonald.com > > > On Mon, Sep 11, 2017 at 7:03 PM, Shazron wrote: > > +1 on console. No PRs for that yet though so it's not ready. > > > > On Tue, Sep 12, 2017 at 5:46 AM, Steven Gill > wrote: > > > >> Console should be released too since it has been moved back into ios for > >> next release. https://issues.apache.org/jira/browse/CB-13170 > >> > >> On Sep 11, 2017 2:04 PM, "Jesse" wrote: > >> > >> > Android release is dependent on us releasing an > >> > updated cordova-plugin-compat > >> > > >> > Anyone have any reasons to not do a release? Anything outstanding > >> > anyone wants to get merged in before moving ahead with a plugins > >> > release? Any other comments on the topic? > >> > > >> > Cheers, > >> > Jesse > >> > > >> > > >> > @purplecabbage > >> > risingj.com > >> > > >> > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: [DISCUSS] Plugin release
Both of: cordova-plugin-device-motion cordova-plugin-device-orientation should get their deprecation PR's merge and also released. Simon Mac Donald http://simonmacdonald.com On Mon, Sep 11, 2017 at 7:03 PM, Shazronwrote: > +1 on console. No PRs for that yet though so it's not ready. > > On Tue, Sep 12, 2017 at 5:46 AM, Steven Gill wrote: > >> Console should be released too since it has been moved back into ios for >> next release. https://issues.apache.org/jira/browse/CB-13170 >> >> On Sep 11, 2017 2:04 PM, "Jesse" wrote: >> >> > Android release is dependent on us releasing an >> > updated cordova-plugin-compat >> > >> > Anyone have any reasons to not do a release? Anything outstanding >> > anyone wants to get merged in before moving ahead with a plugins >> > release? Any other comments on the topic? >> > >> > Cheers, >> > Jesse >> > >> > >> > @purplecabbage >> > risingj.com >> > >> - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: [DISCUSS] Plugin release
+1 on console. No PRs for that yet though so it's not ready. On Tue, Sep 12, 2017 at 5:46 AM, Steven Gillwrote: > Console should be released too since it has been moved back into ios for > next release. https://issues.apache.org/jira/browse/CB-13170 > > On Sep 11, 2017 2:04 PM, "Jesse" wrote: > > > Android release is dependent on us releasing an > > updated cordova-plugin-compat > > > > Anyone have any reasons to not do a release? Anything outstanding > > anyone wants to get merged in before moving ahead with a plugins > > release? Any other comments on the topic? > > > > Cheers, > > Jesse > > > > > > @purplecabbage > > risingj.com > > >
Re: [DISCUSS] Plugin release
There are no PRs, so I think we can release. I saw it has a [DEPRECATED] message in the description tag, maybe we should also add an info tag with a deprecation message so it appears on plugin install? 2017-09-11 23:46 GMT+02:00 Steven Gill: > Console should be released too since it has been moved back into ios for > next release. https://issues.apache.org/jira/browse/CB-13170 > > On Sep 11, 2017 2:04 PM, "Jesse" wrote: > > > Android release is dependent on us releasing an > > updated cordova-plugin-compat > > > > Anyone have any reasons to not do a release? Anything outstanding > > anyone wants to get merged in before moving ahead with a plugins > > release? Any other comments on the topic? > > > > Cheers, > > Jesse > > > > > > @purplecabbage > > risingj.com > > >
Re: [DISCUSS] Plugin release
Console should be released too since it has been moved back into ios for next release. https://issues.apache.org/jira/browse/CB-13170 On Sep 11, 2017 2:04 PM, "Jesse"wrote: > Android release is dependent on us releasing an > updated cordova-plugin-compat > > Anyone have any reasons to not do a release? Anything outstanding > anyone wants to get merged in before moving ahead with a plugins > release? Any other comments on the topic? > > Cheers, > Jesse > > > @purplecabbage > risingj.com >
Re: [DISCUSS] Plugin release this week / early next
SGTM. It has been awhile since our last plugins release. -James Jong On Apr 15, 2014, at 11:53 AM, Ian Clelland iclell...@chromium.org wrote: It's been a while since we did a plugin release, and I have a number of changes to File / Media that I'd like to make public. It looks every plugin has had at least one commit since the last release, though, so maybe we want to do a release of the full suite. (The one minimum commit for each appears to be an Added NOTICE file, so it might be good from an ASF-compliance POV) From what I can see this morning: cordova-plugin-battery-status: release 0.2.8, 1 commit cordova-plugin-camera: release 0.2.9, 12 commits cordova-plugin-console: release 0.2.8, 1 commit cordova-plugin-contacts: release 0.2.10, 5 commits cordova-plugin-device: release 0.2.9, 3 commits cordova-plugin-device-motion: release 0.2.7, 2 commits cordova-plugin-device-orientation: release 0.3.6, 3 commits cordova-plugin-dialogs: release 0.2.7, 5 commits cordova-plugin-file: release 1.0.2, 25 commits cordova-plugin-file-transfer: release 0.4.3, 7 commits cordova-plugin-geolocation: release 0.3.7, 4 commits cordova-plugin-globalization: release 0.2.7, 4 commits cordova-plugin-inappbrowser: release 0.3.4, 12 commits cordova-plugin-media: release 0.2.10, 4 commits cordova-plugin-media-capture: release 0.2.9, 8 commits cordova-plugin-network-information: release 0.2.8, 3 commits cordova-plugin-splashscreen: release 0.2.8, 3 commits cordova-plugin-statusbar: release 0.1.5, 4 commits cordova-plugin-vibration: release 0.3.8, 1 commit I have a couple of changes that I want to get in to media-capture today, but after that I'm happy with the state of the file-related plugins. Thoughts? We could start a vote thread tomorrow or Thursday, and release on Monday if it passes. Ian
RE: [DISCUSS] Plugin release this week / early next
Yes. We need this to happen way more frequently. Sent from my Windows PhoneFrom: James Jong Sent: 4/15/2014 9:17 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Plugin release this week / early next SGTM. It has been awhile since our last plugins release. -James Jong On Apr 15, 2014, at 11:53 AM, Ian Clelland iclell...@chromium.org wrote: It's been a while since we did a plugin release, and I have a number of changes to File / Media that I'd like to make public. It looks every plugin has had at least one commit since the last release, though, so maybe we want to do a release of the full suite. (The one minimum commit for each appears to be an Added NOTICE file, so it might be good from an ASF-compliance POV) From what I can see this morning: cordova-plugin-battery-status: release 0.2.8, 1 commit cordova-plugin-camera: release 0.2.9, 12 commits cordova-plugin-console: release 0.2.8, 1 commit cordova-plugin-contacts: release 0.2.10, 5 commits cordova-plugin-device: release 0.2.9, 3 commits cordova-plugin-device-motion: release 0.2.7, 2 commits cordova-plugin-device-orientation: release 0.3.6, 3 commits cordova-plugin-dialogs: release 0.2.7, 5 commits cordova-plugin-file: release 1.0.2, 25 commits cordova-plugin-file-transfer: release 0.4.3, 7 commits cordova-plugin-geolocation: release 0.3.7, 4 commits cordova-plugin-globalization: release 0.2.7, 4 commits cordova-plugin-inappbrowser: release 0.3.4, 12 commits cordova-plugin-media: release 0.2.10, 4 commits cordova-plugin-media-capture: release 0.2.9, 8 commits cordova-plugin-network-information: release 0.2.8, 3 commits cordova-plugin-splashscreen: release 0.2.8, 3 commits cordova-plugin-statusbar: release 0.1.5, 4 commits cordova-plugin-vibration: release 0.3.8, 1 commit I have a couple of changes that I want to get in to media-capture today, but after that I'm happy with the state of the file-related plugins. Thoughts? We could start a vote thread tomorrow or Thursday, and release on Monday if it passes. Ian
Re: [DISCUSS] Plugin release this week / early next
+1 On Tue, Apr 15, 2014 at 12:24 PM, Jesse MacFadyen purplecabb...@gmail.comwrote: Yes. We need this to happen way more frequently. Sent from my Windows PhoneFrom: James Jong Sent: 4/15/2014 9:17 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Plugin release this week / early next SGTM. It has been awhile since our last plugins release. -James Jong On Apr 15, 2014, at 11:53 AM, Ian Clelland iclell...@chromium.org wrote: It's been a while since we did a plugin release, and I have a number of changes to File / Media that I'd like to make public. It looks every plugin has had at least one commit since the last release, though, so maybe we want to do a release of the full suite. (The one minimum commit for each appears to be an Added NOTICE file, so it might be good from an ASF-compliance POV) From what I can see this morning: cordova-plugin-battery-status: release 0.2.8, 1 commit cordova-plugin-camera: release 0.2.9, 12 commits cordova-plugin-console: release 0.2.8, 1 commit cordova-plugin-contacts: release 0.2.10, 5 commits cordova-plugin-device: release 0.2.9, 3 commits cordova-plugin-device-motion: release 0.2.7, 2 commits cordova-plugin-device-orientation: release 0.3.6, 3 commits cordova-plugin-dialogs: release 0.2.7, 5 commits cordova-plugin-file: release 1.0.2, 25 commits cordova-plugin-file-transfer: release 0.4.3, 7 commits cordova-plugin-geolocation: release 0.3.7, 4 commits cordova-plugin-globalization: release 0.2.7, 4 commits cordova-plugin-inappbrowser: release 0.3.4, 12 commits cordova-plugin-media: release 0.2.10, 4 commits cordova-plugin-media-capture: release 0.2.9, 8 commits cordova-plugin-network-information: release 0.2.8, 3 commits cordova-plugin-splashscreen: release 0.2.8, 3 commits cordova-plugin-statusbar: release 0.1.5, 4 commits cordova-plugin-vibration: release 0.3.8, 1 commit I have a couple of changes that I want to get in to media-capture today, but after that I'm happy with the state of the file-related plugins. Thoughts? We could start a vote thread tomorrow or Thursday, and release on Monday if it passes. Ian
Re: [DISCUSS] Plugin release this week / early next
+1 Ian, what tool did you use to generate that list? Was it manual or.. coho ;) On Tue, Apr 15, 2014 at 9:50 AM, Bryan Higgins br...@bryanhiggins.netwrote: +1 On Tue, Apr 15, 2014 at 12:24 PM, Jesse MacFadyen purplecabb...@gmail.comwrote: Yes. We need this to happen way more frequently. Sent from my Windows PhoneFrom: James Jong Sent: 4/15/2014 9:17 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Plugin release this week / early next SGTM. It has been awhile since our last plugins release. -James Jong On Apr 15, 2014, at 11:53 AM, Ian Clelland iclell...@chromium.org wrote: It's been a while since we did a plugin release, and I have a number of changes to File / Media that I'd like to make public. It looks every plugin has had at least one commit since the last release, though, so maybe we want to do a release of the full suite. (The one minimum commit for each appears to be an Added NOTICE file, so it might be good from an ASF-compliance POV) From what I can see this morning: cordova-plugin-battery-status: release 0.2.8, 1 commit cordova-plugin-camera: release 0.2.9, 12 commits cordova-plugin-console: release 0.2.8, 1 commit cordova-plugin-contacts: release 0.2.10, 5 commits cordova-plugin-device: release 0.2.9, 3 commits cordova-plugin-device-motion: release 0.2.7, 2 commits cordova-plugin-device-orientation: release 0.3.6, 3 commits cordova-plugin-dialogs: release 0.2.7, 5 commits cordova-plugin-file: release 1.0.2, 25 commits cordova-plugin-file-transfer: release 0.4.3, 7 commits cordova-plugin-geolocation: release 0.3.7, 4 commits cordova-plugin-globalization: release 0.2.7, 4 commits cordova-plugin-inappbrowser: release 0.3.4, 12 commits cordova-plugin-media: release 0.2.10, 4 commits cordova-plugin-media-capture: release 0.2.9, 8 commits cordova-plugin-network-information: release 0.2.8, 3 commits cordova-plugin-splashscreen: release 0.2.8, 3 commits cordova-plugin-statusbar: release 0.1.5, 4 commits cordova-plugin-vibration: release 0.3.8, 1 commit I have a couple of changes that I want to get in to media-capture today, but after that I'm happy with the state of the file-related plugins. Thoughts? We could start a vote thread tomorrow or Thursday, and release on Monday if it passes. Ian
Re: [DISCUSS] Plugin release this week / early next
A little bit of both :) Versions from coho foreach grep -o 'version=\.*\' plugin.xml | head -n 2 | tail -n 1 -r plugins Commit counts from coho foreach git log origin/master..origin/dev --oneline | grep -v 'Incremented plugin version' | grep -v 'Merge branch' | wc -l -r plugins and then I collated it manually. On Tue, Apr 15, 2014 at 2:10 PM, Shazron shaz...@gmail.com wrote: +1 Ian, what tool did you use to generate that list? Was it manual or.. coho ;) On Tue, Apr 15, 2014 at 9:50 AM, Bryan Higgins br...@bryanhiggins.net wrote: +1 On Tue, Apr 15, 2014 at 12:24 PM, Jesse MacFadyen purplecabb...@gmail.comwrote: Yes. We need this to happen way more frequently. Sent from my Windows PhoneFrom: James Jong Sent: 4/15/2014 9:17 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Plugin release this week / early next SGTM. It has been awhile since our last plugins release. -James Jong On Apr 15, 2014, at 11:53 AM, Ian Clelland iclell...@chromium.org wrote: It's been a while since we did a plugin release, and I have a number of changes to File / Media that I'd like to make public. It looks every plugin has had at least one commit since the last release, though, so maybe we want to do a release of the full suite. (The one minimum commit for each appears to be an Added NOTICE file, so it might be good from an ASF-compliance POV) From what I can see this morning: cordova-plugin-battery-status: release 0.2.8, 1 commit cordova-plugin-camera: release 0.2.9, 12 commits cordova-plugin-console: release 0.2.8, 1 commit cordova-plugin-contacts: release 0.2.10, 5 commits cordova-plugin-device: release 0.2.9, 3 commits cordova-plugin-device-motion: release 0.2.7, 2 commits cordova-plugin-device-orientation: release 0.3.6, 3 commits cordova-plugin-dialogs: release 0.2.7, 5 commits cordova-plugin-file: release 1.0.2, 25 commits cordova-plugin-file-transfer: release 0.4.3, 7 commits cordova-plugin-geolocation: release 0.3.7, 4 commits cordova-plugin-globalization: release 0.2.7, 4 commits cordova-plugin-inappbrowser: release 0.3.4, 12 commits cordova-plugin-media: release 0.2.10, 4 commits cordova-plugin-media-capture: release 0.2.9, 8 commits cordova-plugin-network-information: release 0.2.8, 3 commits cordova-plugin-splashscreen: release 0.2.8, 3 commits cordova-plugin-statusbar: release 0.1.5, 4 commits cordova-plugin-vibration: release 0.3.8, 1 commit I have a couple of changes that I want to get in to media-capture today, but after that I'm happy with the state of the file-related plugins. Thoughts? We could start a vote thread tomorrow or Thursday, and release on Monday if it passes. Ian
Re: [DISCUSS] Plugin release this week / early next
We should write a coho script for that (*ducks*). On Tue, Apr 15, 2014 at 2:14 PM, Ian Clelland iclell...@google.com wrote: A little bit of both :) Versions from coho foreach grep -o 'version=\.*\' plugin.xml | head -n 2 | tail -n 1 -r plugins Commit counts from coho foreach git log origin/master..origin/dev --oneline | grep -v 'Incremented plugin version' | grep -v 'Merge branch' | wc -l -r plugins and then I collated it manually. On Tue, Apr 15, 2014 at 2:10 PM, Shazron shaz...@gmail.com wrote: +1 Ian, what tool did you use to generate that list? Was it manual or.. coho ;) On Tue, Apr 15, 2014 at 9:50 AM, Bryan Higgins br...@bryanhiggins.net wrote: +1 On Tue, Apr 15, 2014 at 12:24 PM, Jesse MacFadyen purplecabb...@gmail.comwrote: Yes. We need this to happen way more frequently. Sent from my Windows PhoneFrom: James Jong Sent: 4/15/2014 9:17 AM To: dev@cordova.apache.org Subject: Re: [DISCUSS] Plugin release this week / early next SGTM. It has been awhile since our last plugins release. -James Jong On Apr 15, 2014, at 11:53 AM, Ian Clelland iclell...@chromium.org wrote: It's been a while since we did a plugin release, and I have a number of changes to File / Media that I'd like to make public. It looks every plugin has had at least one commit since the last release, though, so maybe we want to do a release of the full suite. (The one minimum commit for each appears to be an Added NOTICE file, so it might be good from an ASF-compliance POV) From what I can see this morning: cordova-plugin-battery-status: release 0.2.8, 1 commit cordova-plugin-camera: release 0.2.9, 12 commits cordova-plugin-console: release 0.2.8, 1 commit cordova-plugin-contacts: release 0.2.10, 5 commits cordova-plugin-device: release 0.2.9, 3 commits cordova-plugin-device-motion: release 0.2.7, 2 commits cordova-plugin-device-orientation: release 0.3.6, 3 commits cordova-plugin-dialogs: release 0.2.7, 5 commits cordova-plugin-file: release 1.0.2, 25 commits cordova-plugin-file-transfer: release 0.4.3, 7 commits cordova-plugin-geolocation: release 0.3.7, 4 commits cordova-plugin-globalization: release 0.2.7, 4 commits cordova-plugin-inappbrowser: release 0.3.4, 12 commits cordova-plugin-media: release 0.2.10, 4 commits cordova-plugin-media-capture: release 0.2.9, 8 commits cordova-plugin-network-information: release 0.2.8, 3 commits cordova-plugin-splashscreen: release 0.2.8, 3 commits cordova-plugin-statusbar: release 0.1.5, 4 commits cordova-plugin-vibration: release 0.3.8, 1 commit I have a couple of changes that I want to get in to media-capture today, but after that I'm happy with the state of the file-related plugins. Thoughts? We could start a vote thread tomorrow or Thursday, and release on Monday if it passes. Ian