-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
v0.12.0 #241
Comments
One hint: give the transifex community some time to translate new strings from merged PRs before merging #240 (Transifex Update) and tagging a new release. Otherwise, there will be many untranslated strings in the release. |
Okay everyone. Have i missed anything? App seems to work fine. @dan0xii can you please give me an update of the widget state? ( Otherwise i think we can merge transifex and release. PS.: @schaarsc and @dan0xii can you please contact me via email at info@niedermann.it? I had recently a conversation with @korelstar and have got some candy for you) |
Before I saw korelstar's comment I was going to suggest leaving #263 until the next release so that 0.12.0 isn't delayed too much but if you're happy to wait then it does make the widget a lot more functional. I've been using it on my phone since I made the PR and haven't encountered any issues. The remaining code to merge is still needed to enable scrolling and basically sets the widget to use a listview with the single textview containing the note content as its child. I've used this to create an "all notes" widget also which I've been running on my phone. This widget has #263 as a prerequisite so I've delayed making a PR until it's merged. |
Aggree, everything should be in I will tag tonight or tomorrow. |
Didn't managed it yesterday, will tag as soon as possible... |
Okay folks,
this is the plan to release the next version!
Pull Requests to merge:
Sorry, #207 Vibrate on list item move and #202 Links between notes will have to wait since there are still discussion points.
After merging those three, we will test for a while and if there no problem occurs, we will tag the version (leads to build on f-droid).
Then we will wait for a while and then release v0.12.0 on Play Store.
CC @schaarsc @dan0xii and of course @korelstar
Thank you very much for your patience. Please solve the remaining conflicts and then let's go 🚀 !
The text was updated successfully, but these errors were encountered: