Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Next beta / feature release

See original GitHub issue

And once again we should find an appropriate point in time to cut off a new feature release by merging master to release.

New features (like quick settings on map) are already there. Not sure though if there are any left over regressions since last release. Some candidates I see:

#9509 #9463

Issue Analytics

State:
Created 3 years ago
Comments:37 (37 by maintainers)

Top GitHub Comments

2reactions

moving-bitscommented, Jan 9, 2021

I checked Play Console statistics for our latest RC. It looks mostly fine, only one message catches me: #9738.

Proposal for continuing with RC and master:

Check if #9738 can be fixed easily, otherwise mitigate by adding try/catch in MfMapView.zoomToViewport
Release from that state
Branch current master to a new release branch (and probably start a new beta in a couple of days)
Merge SAF stuff to master

Should we calculate some time buffer between 2) and 3), if the need for some hotfix should arise?

What do you think?

2reactions

Lineflyercommented, Jan 6, 2021

Seeing that #9687 has been merged, I will brew a new RC tonight give it a bit of smoke test and publish it on the beta channel as an update of the existing 2020.12.22-RC. Afterwards I will filter the support tickets dealing with “open in browser” and ask those beta tester to try the new version.