Status-react: 0.9.33 public mobile release

[pablanopete]

Creating this issue to manage 0.9.33 public release.

open issues and PRs for release: https://github.com/status-im/status-react/labels/release

(template from prior release issues)

GitHub

status-im/status-react

a free (libre) open source, mobile OS for Ethereum - status-im/status-react

[mandrigin]

@pablanopete thanks for creating the issue!

Just for the record, this release will be internal and won't be publicly available. We will target 0.9.34 to be a public release.

[mandrigin]

the release branch is release/0.9.33

[rachelhamlin]

Just for posterity, we discussed an early Feb target for 0.9.34.

The work on device syncing & reliability will be great to have public, since ETHDenver is promoting an #ETHDenver channel in Status.

[pablanopete]

Great thanks for all the information! Updating the title to reflect the public release for coordination, since 0.9.33 will be internally tested.

@mandrigin @rachelhamlin

[rachelhamlin]

Yeah, let's use to manage 0.9.34 instead.

I've begun a list of updates to be included in the release notes, although it's very incomplete.

Easiest thing is probably to ask team leads what updates need to be publicly released since December 6th.
cc @mandrigin @yenda @jeluard @guylouis @goranjovic 👋

[jeluard]

@mandrigin Is the branch you shared for 0.9.34 ? Might be worth renaming it?

[mandrigin]

@jeluard then we can just ignore the internal release. Initially I thought that it makes sense to track internal releases too, but, whatever.

[jeluard]

My bad I didn't know we have internal releases.

[rachelhamlin]

Hey @mandrigin - the token requested for this release should be available by Jan 30th, and it's then a matter of our adding it (hoping @goranjovic can help with that).

In the meantime, I can help to complete the list of everything else we'd like to have included.

(FYI @annadanchenko)

[mandrigin]

@rachelhamlin wasn't the initial deadline for this token end of this week?

[mandrigin]

We will release 0.9.33 in public as well, since Infura hotfix broke our release schedule :)

[rachelhamlin]

That's what we asked for @mandrigin, but the team says the 30th is the latest they'll have it ready. Up to you whether we can wait for that or not. What do you think?

[mandrigin]

Let's see, I don't want to promise anything at that point.

I think that we shouldn't think at this token right now. If it is ready before we release 0.9.33, we can include it (it doesn't look like a lot of work to me). If not — maybe we can make a hotfix with just this token afterwards.

What do you think @annadanchenko @rachelhamlin?

[rachelhamlin]

Yup, I think that works great. If it makes sense otherwise to start on this release, I don't want to delay for a non-urgent issue.

cc @pablanopete

[annadanchenko]

closing as release 0.9.33 is out