Looking at iOS 2.9.0:

Definitely as you said: https://issues.apache.org/jira/browse/CB-3757
Then all iOS cli and docs issues.

If there is time for iOS I am going to tackle:
https://issues.apache.org/jira/browse/CB-3303 (to fix)
https://issues.apache.org/jira/browse/CB-3451 (to investigate, no fix yet)
https://issues.apache.org/jira/browse/CB-3567 (there is a PR to investigate)
https://issues.apache.org/jira/browse/CB-3562 (fix in the issue, to
evaluate)
https://issues.apache.org/jira/browse/CB-3534 (the reporter has filed an
excellent bug report, to repro, and maybe fix)

Maybe this Untappd issue: https://issues.apache.org/jira/browse/CB-3574



On Thu, Jun 13, 2013 at 11:10 AM, Lorin Beer <lorin.beer....@gmail.com>wrote:

> be the leaf in the wind, Shaz.
>
> Anything pressing on iOS that needs to be resolved? I am aware of a bug in
> Camera, which I can take a look at. Anything else you want in?
>
>
> On Thu, Jun 13, 2013 at 11:01 AM, Shazron <shaz...@gmail.com> wrote:
>
> > I wish I could say there was more velocity in the iOS / OS X repos but
> > there hasn't been any with me being away at WWDC this week, but if that's
> > where the wind blows I am but a feather. Will try to get more issues
> > resolved by rc2.
> >
> >
> > On Thu, Jun 13, 2013 at 9:27 AM, Lorin Beer <lorin.beer....@gmail.com
> > >wrote:
> >
> > > +1, let's tackle this early
> > >
> > >
> > > On Wed, Jun 12, 2013 at 4:06 PM, Jesse <purplecabb...@gmail.com>
> wrote:
> > >
> > > > meh
> > > >
> > > > @purplecabbage
> > > > risingj.com
> > > >
> > > >
> > > > On Wed, Jun 12, 2013 at 4:03 PM, Filip Maj <f...@adobe.com> wrote:
> > > >
> > > > > Huge +1!
> > > > >
> > > > > On 6/12/13 3:56 PM, "Joe Bowser" <bows...@gmail.com> wrote:
> > > > >
> > > > > >Hey
> > > > > >
> > > > > >I know this is pretty soon, but how does a 2.9.0rc1 on Monday
> sound?
> > > > > >Since this is supposed to be a hardening release anyway, I don't
> see
> > > > > >why we shouldn't start with the RCs.
> > > > > >
> > > > > >Any thoughts?
> > > > > >
> > > > > >Joe
> > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to