Re: Tagging 3.1.0 today?

What else can I help with to get this thing out the door? On Oct 1, 2013, at 12:05 AM, Marcel Kinard wrote: > I believe the docs are now done.

Re: Review Request 14356: Plugins Release draft blog post

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14356/#review26558 --- Ship it! Looks good! Don't forget to run "rake build" before commit

Re: Plugman Release

Braden's out doing intern interviews yesterday & today, so it's unlikely he'll see this email until tomorrow if not Thursday. We could still do a tools release, but just don't update the platforms.js file to point at 3.1.0. That said, I think I saw Firefox was broken on HEAD? Think we'll want to f

Re: Tagging 3.1.0 today?

Tough call. I think there are pros/cons either way. On Tue, Oct 1, 2013 at 5:16 AM, Marcel Kinard wrote: > I noticed that cordova-docs wasn't tagged or branched at the same time the > platforms were branched into 3.1.x for rc1. This seems to leave open the > possibility for docs from platforms/

Re: Tagging 3.1.0 today?

Thanks for pointing this out Peter - filed CB-4965. On Tue, Oct 1, 2013 at 6:46 AM, Smith, Peter wrote: > Don't know if this is related to the 'leaking docs' scenario, but FYI > when we fetched the official 3.0 source zip download yesterday we saw > there are some inconsistencies between the doc

Re: Hello Apache Team

Awesome! Looking forward to your help on the project! On Tue, Oct 1, 2013 at 6:50 AM, Maxime LUCE wrote: > CLA already filled and sent to secret...@apache.org. > > > Cordialement. > Maxime LUCE > max...@touchit.fr > 06 28 60 72 34 > http://touchit.fr > > > -Original Message- > From: Jes

Re: Tagging 3.1.0 today?

Okay, I've finally got time again to focus on this. I'm fine with skipping an RC announcement this time around. I'm pretty confident that the current state of 3.1 is better than 3.0 :). Docs & upgrade guides look great! Thanks Marcel. I've just tagged 3.1.0 for JS+MobileSpec+HelloWorld. I think a

Mobilespec / CI / version problems

Summary: Due to the renaming of plugins, there is no longer a sensible way to test 3.0.x Detail: The process to test 3.0.x is to get platforms, mobile-spec, etc from 3.0.x and plugins from master. With the change on plugin names (remove core) the 3.0.x mobile-spec still refers to the names with co

Re: Mobilespec / CI / version problems

In the past I've used #3. When checking out code to test, I try to get all the assets from the same branch / time period. But I may be skewed in that approach, since our product that embeds Cordova has a snapshot of the platforms and plugins, and doesn't get updates from the online repos. Does

Re: Review Request 14356: Plugins Release draft blog post

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14356/#review26560 --- Ship it! Where you say that a new plugin release is being performed

Re: Mobilespec / CI / version problems

The issue is the that stated methodology for getting the right versions to test is: * for release, get plugins from the master branch and platforms, tests etc from the release branch (3.0.x) * for tip of tree, get plugins from the dev branch and platforms, tests etc from the master branch Since the

Re: Mobilespec / CI / version problems

Would it fix it to use mobile-spec from master when testing 3.0.x? Mobile-spec generally stays in sync with the plugins more so than the platforms, so it would make sense to me to use mobile-spec at master if using plugins from master/dev. On Tue, Oct 1, 2013 at 4:40 PM, David Kemp wrote: > The

RE: Hello Apache Team

Hello, Just a question. I saw my pull request have been merged into cordova-plugin-transfer's dev branch. May I wait the merge of dev branch into master branch to close pull request on Github ? Same question about the issue in JIRA ? Thanks Cordialement. Maxime LUCE max...@touchit.fr 06 28 60

Re: Plugman Release

Firefoxos is broken on master after the refactor. It works fine on the cordova-3.1.x branch though. I am testing jesse's pull requests for CLI + plugman today for cordova-3.1.x branch. If they look good I will merge them in. We should release CLI + Plugman at the same time as 3.1.0. The release sh

Re: Mobilespec / CI / version problems

I believe that will be OK - testing it out now. It still probably deserves some documentation somewhere that the previously stated relationships don't work anymore, and that any plugin references in a 3.0.x project need attention. On Tue, Oct 1, 2013 at 12:03 PM, Andrew Grieve wrote: > Would

Re: Mobilespec / CI / version problems

Aren't we testing 3.1.0 with the tests that were tagged in 3.1.0? Testing with 3.0.0 tests seems like you'll always have failing tests, since ideally the tests should have been added with the bug (although I don't know where to put platform-specific mobile-spec tests, the don't really have a home a

Re: Hello Apache Team

Great. You should close the pull requests and close the JIRA issue now. On Tue, Oct 1, 2013 at 5:13 PM, Maxime LUCE wrote: > Hello, > > Just a question. > I saw my pull request have been merged into cordova-plugin-transfer's dev > branch. > May I wait the merge of dev branch into master branch

Re: Tagging 3.1.0 today?

If any platform owners don't have time to do this today, let me know how I can help. On Oct 1, 2013, at 11:11 AM, Andrew Grieve wrote: > I think all that needs > to happen now is for all platform owners to update their JS snapshot again > and push a "3.1.0" tag.

Re: Mobilespec / CI / version problems

I am running regression tests on 3.0.x as well as tests on the tip of tree. I have not yet switched to running regression on 3.1.x since it isn't actually released yet. The problem is that suddenly the 3.0.x tests fail. This is mostly because the plugins are not tied to a release, but mobilespec i

Re: Mobilespec / CI / version problems

In answer to Andrews response, there was a problem with 3.0.x where the echo plugin was mostly removed, but the two source files CDVEcho.m, CDVEcho.h were left in iOS core. When you build 3.0.x with the master version (or 3.1.x) of Mobilespec and it includes the new Echo plugin, you get duplicate s

Re: Tagging 3.1.0 today?

Since I believe Lorin is away, I have tagged the release for blackberry. On 13-10-01 1:01 PM, "Marcel Kinard" wrote: >If any platform owners don't have time to do this today, let me know how >I can help. > >On Oct 1, 2013, at 11:11 AM, Andrew Grieve wrote: > >> I think all that needs >> to happ

Re: Mobilespec / CI / version problems

Just for clarification... Testing 3.1.x works fine using 3.1 platforms, 3.1 mobilespec, and master plugins. Testing 'HEAD' works fine using master platforms, master mobilespec, and dev plugins. Thats all as expected. Up until a week ago, you could test 3.0.x using 3.0.x platforms, 3.0.x mobilesp

Re: Tagging 3.1.0 today?

Just tagged Android. There's some weird inconsistencies across devices, but overall the platform itself still seems solid. There's nothing here that would prevent a release. We should really start that API audit though. These inconsistencies don't make me super confident in the plugins. :( On

Re: Tagging 3.1.0 today?

Going to tag iOS within the next hour. On Tuesday, October 1, 2013, Joe Bowser wrote: > Just tagged Android. There's some weird inconsistencies across > devices, but overall the platform itself still seems solid. There's > nothing here that would prevent a release. > > We should really start th

Tag 2.9.1

As soon as we are done with 3.1.0 it would be a good time to go back and back-fill for a 2,9,1 release. Who's with me? Do we need to do an RC? If so, a quick one? Cheers, Jesse @purplecabbage risingj.com

Re: Plugman Release

It seems as though there is no cordova-cli 3.1.x branch, does this mean we always release off of master? There is a bug I found where element tree needs to be bumped to the same version as plugman to support namespace xml elements and I'd like to know where to push this. Thanks, Jeff On 13-10-0

Re: Tagging 3.1.0 today?

Just curious, will there be a plugins release today to coincide, or will that be done on a different date (and if so, what day, Thursday)?

Re: Tag 2.9.1

Have we done RCs for minor releases before? I don't recall any for 3.0.1 to 3.0.9, and I can't see anything in my email archives from 2.6.1 or 2.8.1. Not that it's a bad idea; I just don't think it's a formality that has been observed in the past. How much back-fill are you expecting? On Tue,

Re: Tagging 3.1.0 today?

Shaz - there were several changes to the project template for Xcode 5. Do you know if any of them are necessary to mention in the upgrade guide? On Tue, Oct 1, 2013 at 7:27 PM, Shazron wrote: > Going to tag iOS within the next hour. > > On Tuesday, October 1, 2013, Joe Bowser wrote: > > > Just

Re: Tagging 3.1.0 today?

Yup! Plugins got released last week. I will be posting the blog for it today. Once platforms are tagged, I can look into assembling the distribution. On Tue, Oct 1, 2013 at 12:34 PM, Andrew Grieve wrote: > Steve should clarify - but I think he did a plugins release last week and > just needs t

Re: Tagging 3.1.0 today?

One failure in Media plugin (set position) for both iOS 6 and 7. Should this hold the release up? I would say no since we can always update the plugin. Unfortunately the splashscreen plugin has a typo (my bad) that results in a visual failure on iOS 6 (decrementing a value twice): https://git-wip-

Re: Tagging 3.1.0 today?

Steve should clarify - but I think he did a plugins release last week and just needs to upload the blog post for it? On Tue, Oct 1, 2013 at 8:32 PM, Marcel Kinard wrote: > Just curious, will there be a plugins release today to coincide, or will > that be done on a different date (and if so, wha

Re: Tagging 3.1.0 today?

Most of them are GCC and Clang warning settings (that are set to YES when upgrading the project template) but they can get this upgrade when Xcode prompts them to upgrade. The only relevant setting is changing the compiler to "" (default) instead of hard-coding it from before: https://git-wip-us.a

Re: Tagging 3.1.0 today?

I would suggest doing all of your work in dev and don't worry about cherry picking into master. We can do another plugin release early next week where we merge into master, tag and reupload to plugins.cordova.io. We did plan on doing a release on a weekly basis if I recall correctly. Thoughts? If

Re: Tagging 3.1.0 today?

On Tue, Oct 1, 2013 at 3:39 PM, Shazron wrote: > One failure in Media plugin (set position) for both iOS 6 and 7. Should > this hold the release up? I would say no since we can always update the > plugin. > Agreed -- plugins should be independent of core; we can fix this soon and release cordova

Review Request 14429: 3.1 release blog post

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14429/ --- Review request for cordova. Repository: cordova-site Description --- 3.1

Re: Tagging 3.1.0 today?

Alright - i'll just checkin to dev, and let's worry about the decision for an updated plugin release for later. On Tue, Oct 1, 2013 at 12:46 PM, Steven Gill wrote: > I would suggest doing all of your work in dev and don't worry about cherry > picking into master. We can do another plugin releas

Re: Plugman Release

the branch for both CLI and Plugman is called cordova-3.1.x (don't know why we didn't call it 3.1.x instead) On Tue, Oct 1, 2013 at 12:04 PM, Jeffrey Heifetz wrote: > It seems as though there is no cordova-cli 3.1.x branch, does this mean we > always release off of master? > > There is a bug I f

Re: Tagging 3.1.0 today?

Awesome! FYI - I tweaked the "rake build" and "rake serve" logic today to not suck so much. It will no longer delete .svn directories, and `serve` will now never overwrite files within public/. Let me know if you have issues. On Tue, Oct 1, 2013 at 8:37 PM, Steven Gill wrote: > Yup! Plugins got

Re: Tagging 3.1.0 today?

Blog post drafted, but it's missing highlights for Windows Phone, BlackBerry and FFOS (I based them on RELEASENOTES.md). Can I have volunteers to write up those sections? https://reviews.apache.org/r/14429/ On Tue, Oct 1, 2013 at 8:52 PM, Andrew Grieve wrote: > Awesome! FYI - I tweaked the "ra

Re: ios commit: Delete some incorrect RELEASENOTES.md entries

Not sure why those are in there, I specified 3.0.0...3.1.x On Tue, Oct 1, 2013 at 12:29 PM, wrote: > Updated Branches: > refs/heads/master cc01343e1 -> 246f8e56c > > > Delete some incorrect RELEASENOTES.md entries > > > Project: http://git-wip-us.apache.org/repos/asf/cordova-ios/repo > Commit

Re: Tagging 3.1.0 today?

For my customers, splashscreen is pretty important. How about doing the plugin release tomorrow, at least for this plugin? +1 for Media set-position being published at a later time. On Oct 1, 2013, at 3:46 PM, Steven Gill wrote: > Thoughts? > > If you feel the changes need to get in ASAP, we

Re: ios commit: Delete some incorrect RELEASENOTES.md entries

I think likely those were the cherry-picks. On Tue, Oct 1, 2013 at 8:54 PM, Shazron wrote: > Not sure why those are in there, I specified 3.0.0...3.1.x > > > On Tue, Oct 1, 2013 at 12:29 PM, wrote: > > > Updated Branches: > > refs/heads/master cc01343e1 -> 246f8e56c > > > > > > Delete some i

Re: Tagging 3.1.0 today?

Marcel - just want to better understand what you're doing - Are you distributing the plugins yourself? Or are you having your customers get them from the plugin repository / git URL? On Tue, Oct 1, 2013 at 9:00 PM, Marcel Kinard wrote: > For my customers, splashscreen is pretty important. How

Re: Tagging 3.1.0 today?

iOS tagged. I'm updating the iOS Upgrade Guide to include the default compiler thing, then I'm working on updating the iOS splashscreen code, then testing. On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard wrote: > For my customers, splashscreen is pretty important. How about doing the > plugin rel

Re: Tag 2.9.1

Nope, I don't think we've ever done minor rc's, this is a bit more of a significant release though. Back-fill would just be putting all the updated plugin native code back into each platform, as well as making sure any relevant js changes went back into cordova-js before being tagged+built. Kind o

Re: Tagging 3.1.0 today?

windows8, windows phone 7 + 8 all updated and tagged. I will have some info to add to the blog post for these platforms shortly. @purplecabbage risingj.com On Tue, Oct 1, 2013 at 1:04 PM, Shazron wrote: > iOS tagged. I'm updating the iOS Upgrade Guide to include the default > compiler thing, t

Re: Tagging 3.1.0 today?

I will write up the BlackBerry notes. On Tue, Oct 1, 2013 at 4:12 PM, Jesse wrote: > windows8, windows phone 7 + 8 all updated and tagged. > I will have some info to add to the blog post for these platforms shortly. > > @purplecabbage > risingj.com > > > On Tue, Oct 1, 2013 at 1:04 PM, Shazron

Re: Tag 2.9.1

Right. I wasn't sure if there were 10 issues to backport or 150. If there are only a few isolated fixes to apply, then I'd be comfortable with just applying them, testing and releasing. If there are a ton of fixes, which might have overlapping effects, then lets spend a day or so with a tagged rc a

Re: Tagging 3.1.0 today?

Added http://git-wip-us.apache.org/repos/asf/cordova-docs/commit/d0fdfe5ato cordova-docs, needs a 3.1.0 re-tag. On Tue, Oct 1, 2013 at 1:12 PM, Jesse wrote: > windows8, windows phone 7 + 8 all updated and tagged. > I will have some info to add to the blog post for these platforms shortly. > > @

Re: Tagging 3.1.0 today?

I shall do FFOS tag + write up On Tue, Oct 1, 2013 at 1:15 PM, Bryan Higgins wrote: > I will write up the BlackBerry notes. > > > On Tue, Oct 1, 2013 at 4:12 PM, Jesse wrote: > > > windows8, windows phone 7 + 8 all updated and tagged. > > I will have some info to add to the blog post for these

Re: Tagging 3.1.0 today?

The plugins get distributed by us with the platforms. So I'm creating a static snapshot. The customer's environment does not do a fetch from repository/git. This is why I'm interested in having a "good point in time". On Oct 1, 2013, at 4:04 PM, Andrew Grieve wrote: > Marcel - just want to bet

Re: Tagging 3.1.0 today?

ios splashscreen re-fix tested and pushed to dev. On Tue, Oct 1, 2013 at 1:00 PM, Marcel Kinard wrote: > For my customers, splashscreen is pretty important. How about doing the > plugin release tomorrow, at least for this plugin? > > +1 for Media set-position being published at a later time. >

Re: Tagging 3.1.0 today?

I could cherrypick Shaz's fix into my snapshot if doing a plugin release tomorrow would be undesireable. On Oct 1, 2013, at 4:00 PM, Marcel Kinard wrote: > For my customers, splashscreen is pretty important. How about doing the > plugin release tomorrow, at least for this plugin?

Re: Tagging 3.1.0 today?

Yeah, I think cherry-picking would be the way to go. You'll also want to add url= and subdir= attributes to the tags within the plugins, or else installing them will hit the registry for the dependents (this is the current case). I'd like to add a way to have a local map of plugin ID -> local di

Re: Tagging 3.1.0 today?

Here is the BB write-up. There have been 48 commits to the BlackBerry platform since 3.0.0. Many performance and stability improvements were introduced. Other notable changes include: [CB-4876](https://issues.apache.org/jira/browse/CB-4876) removal of playbook implementation [CB-4812](https://iss

Re: Tagging 3.1.0 today?

Shaz, do you want to take care of that, or would you like me to? When doing a re-tag, do we do the sane thing (use a modified tag name) or the insane thing (reuse the same tag name)? Looks like you already put the change in both the en/edge and en/3.1.0 dirs. Nice. On Oct 1, 2013, at 4:16 PM,

Re: Tagging 3.1.0 today?

Do you mind doing it? I think we've always deleted and re-tagged using the same name On Tue, Oct 1, 2013 at 1:59 PM, Marcel Kinard wrote: > Shaz, do you want to take care of that, or would you like me to? > > When doing a re-tag, do we do the sane thing (use a modified tag name) or > the insane

Re: Tagging 3.1.0 today?

FFOS is tagged. Looks like windows platforms and blackberry have been tagged as well. I saw the tags on the repos and went ahead and closed the issues. Let me know if you guys didn't want those issues closed just yet. Only things remaining are retagging docs, tagging cli, tagging plugman, uploadi

Mapping plugin ID -> URL

There is a need to have plugman look in places other than the registry when fetching plugins by ID. This is particularly the case because plugins now have IDs only instead of specifying a URL. Downstream distributions need this (e.g. IBM packages plugins with their distro). But this would be nice

Re: Tagging 3.1.0 today?

On Tue, Oct 1, 2013 at 10:40 PM, Steven Gill wrote: > FFOS is tagged. > > Looks like windows platforms and blackberry have been tagged as well. I saw > the tags on the repos and went ahead and closed the issues. Let me know if > you guys didn't want those issues closed just yet. > > Only things r

Re: Tagging 3.1.0 today?

David Kemp's buoldbot found a bug in cli from the plugman bump. I have a fix upcoming Sent from my BlackBerry 10 smartphone on the Rogers network. From: Andrew Grieve Sent: Tuesday, October 1, 2013 5:47 PM To: dev Reply To: dev@cordova.apache.org Subject: Re: Tagging 3.1.0 today? On Tue, Oct 1,

Re: Tagging 3.1.0 today?

According to http://wiki.apache.org/cordova/VersioningAndReleaseStrategy, it looks like we were leaning towards CadVer-SemVer for the CLI. I just think it would be weird to only make it CadVer for this release and then add on the SemVer part whenever we make little fixes for the weekly release. O

Re: Mapping plugin ID -> URL

So wait, the use case is proj level deps not plugin level? On Oct 1, 2013 10:50 PM, "Andrew Grieve" wrote: > There is a need to have plugman look in places other than the registry when > fetching plugins by ID. This is particularly the case because > plugins now have IDs only instead of specifyi

Re: Mapping plugin ID -> URL

E.g. for mobile-spec's dependency-plugin, it has Instead of having plugman download it from the registry, I'd like to tell it to look for it locally. Not entirely sure what you mean by project level deps (do those exist)? On Wed, Oct 2, 2013 at 12:45 AM, Brian LeRoux wrote: > So wait, the use

Re: Review Request 14429: 3.1 release blog post

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14429/ --- (Updated Oct. 2, 2013, 12:47 a.m.) Review request for cordova. Repository: co

Re: Tagging 3.1.0 today?

Jeff - is there a JIRA issue for the bug? Would be good to mark it as a dependent of https://issues.apache.org/jira/browse/CB-4843. Bryan - thanks for the write-up! I've updated the review request with your blurb. Steven - CadVer-SemVer sounds good. On Tue, Oct 1, 2013 at 10:53 PM, Steven Gill

Re: Tagging 3.1.0 today?

Looks like Jeff already pushed it. I am updating cordova-3.1.x right now On Tue, Oct 1, 2013 at 5:49 PM, Andrew Grieve wrote: > Jeff - is there a JIRA issue for the bug? Would be good to mark it as a > dependent of https://issues.apache.org/jira/browse/CB-4843. > > Bryan - thanks for the write-

Re: Tagging 3.1.0 today?

Here is a brief summary for wp7 + wp8 and windows8 Windows Phone 7 + 8 Platform updates === Defects closed: CB-3177 remove support in config.xml and remove deprecation notice in WP8 CB-3176 remove support in config.xml and remove deprecation notice in WP7 CB-4385 Tooling scripts fail when the

Re: Review Request 14429: 3.1 release blog post

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14429/#review26578 --- /cordova/site/www/_posts/2013-10-01-cordova-31.md

Re: Tagging 3.1.0 today?

I thought that I had done everything for the blog review earlier, but apparently I missed the "hit the publish button" step. >:( I found one doc issue -- the whitelist docs haven't been updated for iOS and Android, and it's a potentially breaking change, so I'd like to get those updates pushed, an

Re: Tagging 3.1.0 today?

Sounds good. Add it to the docs and lets make sure it makes it in the 3.1.0 blog post On Tue, Oct 1, 2013 at 7:27 PM, Ian Clelland wrote: > I thought that I had done everything for the blog review earlier, but > apparently I missed the "hit the publish button" step. >:( > > I found one doc issu

Re: Tagging 3.1.0 today?

I have updated the cordova-3.1.x branches for the CLI and Plugman. I believe they are both ready to be published on npm. I can publish plugman but I am not listed as a maintainer for the CLI. Can someone either add me as a maintainer for cordova on NPM or publish it for me? My NPM username is ste

Re: Review Request 14429: 3.1 release blog post

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/14429/#review26594 --- Firefox OS Platform updates === Firefox OS support has been added t

RE: Tagging 3.1.0 today?

About File Transfer plugin : Will the dev branch be merged into 3.1 branch before plugins release ? I see some issues in Windows 8 proxy which are resolved in dev branch and not in 3.1 one. Cordialement. Maxime LUCE max...@touchit.fr 06 28 60 72 34 http://touchit.fr -Original Message--

RE: Tagging 3.1.0 today?

We did a plugins release last week. This will have to wait until the next plugins release which could be later this week or next On Oct 1, 2013 10:49 PM, "Maxime LUCE" wrote: > About File Transfer plugin : > Will the dev branch be merged into 3.1 branch before plugins release ? > > I see some iss