Skip to content

Urgent issues that should ideally be fixed before final publicity step #693

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
5 of 6 tasks
misaochan opened this issue May 28, 2017 · 1 comment
Closed
5 of 6 tasks

Comments

@misaochan
Copy link
Member

misaochan commented May 28, 2017

As requested by @neslihanturan . :) I get that we can use labels, but the list itself is up for discussion, so instead of discussing it on the individual issues, we can discuss the general plans here.

My intended date to start the final publicity step (PR releases to general media, as I have already written for the Wikimedia blog and approached blogs that have written about us before) is 5 June 2017 or thereabouts. So the list needs to be attainable within a short period of time, no big suggestions please unless you think you may be able to pick the task up yourself. :)

My suggested tasks:

@misaochan
Copy link
Member Author

misaochan commented Jun 5, 2017

I've just pushed v2.4.2 to beta, should be available in a few hours. Tested manually on API 21, API 23 and API 25, everything seems to work as intended for me. We've managed to fix everything on this list except for #674 , but we can live with that. :)

Please help test 2.4.2 if at all possible. If all goes well, I'll push that to production in a few days' time, then finally everyone can access the new features that we worked on during the hackathon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant