-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
add task to release doc to document appstore releases centrally on pages repo #4251
add task to release doc to document appstore releases centrally on pages repo #4251
Conversation
after all appstores are done: | ||
- [ ] add/update entry on https://github.com/deltachat/deltachat-pages/blob/main/releases.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iirc, the idea of releases.md
is to see at one glance the status of releases for all distribution channels. so, what is really out there :)
to achieve that, it may be needed to update releases.md
if not all stores are done. there are not-so-rarely channels that get stuck for weeks. or do not get a release at all. one wants to see see that eg. that core123 is available on macOS - but stock on Windows for $reasons. or that android456 is out on Google Play - but not on F-droid since weeks
so, maybe a bit more neutral here:
after all appstores are done: | |
- [ ] add/update entry on https://github.com/deltachat/deltachat-pages/blob/main/releases.md | |
update <https://github.com/deltachat/deltachat-pages/blob/main/releases.md> on progress |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I bet that if it is not a todo item it will be forgotten.
There is always the release progress issue on desktop, so if you want to know the state of the release, better look there directly. we could also establish that the latest release progress issue should be pinned for easier access.
iirc, the idea of releases.md is to see at one glance the status of releases for all distribution channels. so, what is really out there :)
I see the use case more in finding out fast, what core version was used based on ui version without checking the long UI changelog easily. for checking what is delayed there is the release progress issue on desktop.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the use case more in finding out fast, what core version was used based on ui version without checking the long UI changelog easily
if that is the gist, indeed on desktop that information is hard to find.
on android/ios we always add a "update to core123" or "using core123" to the end of each changelog entry, so we could just add a link to the changelog from release.md
then.
but anyways, it is also about what is doable, and yes, a concrete checkpoint is better than a vague additional sentence.
so, feel free to merge that in, it is definetely an improvement to add a hint to release.md
. i was just wondering about the gist.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if that is the gist, indeed on desktop that information is hard to find.
To be honest, I don't know what hocuri and Holger thought when making it, this just my interpretation for what I'd use that file.
No description provided.