-
Notifications
You must be signed in to change notification settings - Fork 3
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
Timestamp formatting #47
Conversation
(In case building fails, this is probably because the latest |
True. How long does this take? |
50899bc
to
40ec97b
Compare
Works now. (Usually takes around an hour.) |
For me, increasing the API level is important to document in the changelog.
The reason: I often use old and recycled phones. Increasing the minimum API level excludes users.
|
It already is part of the changelog, see diff 🙂 |
when will this be released? I'd really like to have this feature- as of now I keep copying the lastchange and pasting it in epochconverter online, which is a bit of a pain |
Good question. I wonder what the release process looks like. I guess, F-droid just uses tags.
|
I'm in vacations right now until mid-October. I have the Google Play signing key at home. For F-Droid however, I think a version bump and tag should be sufficient. I can do that in the coming 2-3 days.
Am Fr, 29. Sep 2023, um 13:58, schrieb Nicco Kunzmann:
…
Good question. I wonder what the release process looks like. I guess, F-droid just uses tags.
—
Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAZVUFVLENK76NEKKLUKJTX42ZW3ANCNFSM6AAAAAA4I3CFQU>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Done. Now we need to wait for F-Droid to pick up the new tag. |
Show state "last change" timestamp as localized datetime.
Fixes #46.