For reference: on IRC we decided to do the next
release with all the bug
fixes, but without the references. Since gerrit is being a ROYAL PAIN about
cherry-picking to branches, we're accomplishing this by temporarily
disabling the references code on master and branching there.
-- brion
On Fri, Aug 1, 2014 at 11:35 AM, Dan Garry <dgarry(a)wikimedia.org> wrote:
We should definitely make it as small as
possible. Our goal here is just
to fix the bugs, nothing more. That way we're less likely to introduce
additional bugs. We can get the features out later. :-)
Dan
On 1 August 2014 11:34, Brion Vibber <bvibber(a)wikimedia.org> wrote:
Yep, if we do a more conservative release
I'll want to back port at
least the back-button fixes and that crash workaround. :) I'm investigating
saved pages now...
-- brion
On Fri, Aug 1, 2014 at 11:11 AM, Tomasz Finc <tfinc(a)wikimedia.org>
wrote:
> On Fri, Aug 1, 2014 at 10:57 AM, Brion Vibber <bvibber(a)wikimedia.org>
> wrote:
> > Dan, Tomasz is recommending that for our next push we do a small bug
> fix
> > iteration from the first release branch, rather than landing all the
> stuff
> > we've worked on in the last couple weeks right away.
>
> We're discussing this on IRC right now if you would like to join Dan.
> No decision has been made. I want to make sure we have confidence in
> what we push out and that we don't introduce new issues.
>
> > Do we want to push both "small" and "large" updates to
TestFlight or
> should
> > we just send the "small" version?
>
> --tomasz
>
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation