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 <stevengil...@gmail.com> 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 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 you feel the changes need to get in ASAP, we can bump up the plugin > release to tomorrow. Nothing like two plugin releases in one week :P > > -Steve > > > On Tue, Oct 1, 2013 at 12:39 PM, Shazron <shaz...@gmail.com> 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. > > > > 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-us.apache.org/repos/asf?p=cordova-plugin-splashscreen.git;a=blobdiff;f=src/ios/CDVSplashScreen.m;h=8159ce17bda7a4d10277aa4cbc132fa2c8e6e39d;hp=ba8d108b725f1a1d2331f8e8fc56627aac929ba5;hb=1111c8b3b9b8fe28d6c9fe9c9a1bc548a679e4ac;hpb=5f83eda5e829ac7a11e1803de653cb7cf95764af > > > > I will have to patch that in dev and probably cherry-pick(?) into master > - > > how will this go? > > > > iOS 6 > > one failure - Media media.spec.12 position should be set properly > > Expected 0 to be greater than 0 > > > > iOS 7 > > one failure - Media media.spec.12 position should be set properly > > Expected -0.023 to be greater than 0 > > > > > > > > On Tue, Oct 1, 2013 at 11:27 AM, Shazron <shaz...@gmail.com> wrote: > > > > > 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 that API audit though. These inconsistencies > > >> don't make me super confident in the plugins. :( > > >> > > >> On Tue, Oct 1, 2013 at 10:27 AM, Jeffrey Heifetz > > >> <jheif...@blackberry.com> wrote: > > >> > Since I believe Lorin is away, I have tagged the release for > > blackberry. > > >> > > > >> > On 13-10-01 1:01 PM, "Marcel Kinard" <cmarc...@gmail.com> 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 <agri...@chromium.org> > > >> 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. > > >> >> > > >> > > > >> > > --------------------------------------------------------------------- > > >> > 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. > > >> > > > >> > > > > > >
