Yes, it does.
On Mon, Sep 30, 2013 at 11:04 AM, Jeffrey Heifetz <[email protected]> wrote: > BlackBerry10 needs a commit into CordovaJS for 3.1 as well. (Does this > mean all platforms must be updated?) > > On 13-09-30 1:38 PM, "Shazron" <[email protected]> wrote: > >>iOS has a bug fix that is not in RC1 (but in the 3.1.x branch) related to >>the Keyboard preferences in iOS 7 (visual bug). This is why I've already >>made the prefs into a plugin. Technically they can at a later date use >>this >>plugin as well (plugin not released yet). >> >> >>On Mon, Sep 30, 2013 at 10:34 AM, Joe Bowser <[email protected]> wrote: >> >>> The problem is now we're totally off cadence. I'm currently fine with >>> releasing the RC1 as a release, since this is a platform release and >>> the bugs appear to be based in the plugins. Since the plugins are >>> decoupled, we should be able to go forward once we see the tests pass. >>> >>> On Mon, Sep 30, 2013 at 10:26 AM, Andrew Grieve <[email protected]> >>> wrote: >>> > I was a super bad Release Master last week, and didn't do a thing >>>about >>> the >>> > release. >>> > >>> > Looking at https://wiki.apache.org/cordova/CuttingReleases, looks like >>> we're >>> > in the "Testing & Documentation" section now. Not sure to what extent >>> each >>> > of the RCs has been tested, but the Upgrade Guide still needs >>>updating. >>> > >>> > I would have liked to announce the RC on the blog to get more external >>> > testing of it. Probably it's still a good idea to do this. Not sure >>>I'll >>> get >>> > to it by the end of today though (my Google performance review tasks >>>are >>> > overdue) >>> > >>> > >>> > On Mon, Sep 30, 2013 at 5:51 PM, Joe Bowser <[email protected]> wrote: >>> >> >>> >> Hey >>> >> >>> >> Are we doing a release? I don't see any reason why not from an >>>Android >>> >> standpoint, since only one issue was merged in from RC1. >>> >> >>> >> Joe >>> > >>> > >>> > > --------------------------------------------------------------------- > This transmission (including any attachments) may contain confidential > information, privileged material (including material protected by the > solicitor-client or other applicable privileges), or constitute non-public > information. Any use of this information by anyone other than the intended > recipient is prohibited. If you have received this transmission in error, > please immediately reply to the sender and delete this information from your > system. Use, dissemination, distribution, or reproduction of this > transmission by unintended recipients is not authorized and may be unlawful. >
