search

MM2-0 / Kvaesitso

A search-focused Android launcher
https://kvaesitso.mm20.de/
GNU General Public License v3.0
2.38k stars 74 forks source link

Fastlane changelogs have oversize #849

Open IzzySoft opened 4 months ago

IzzySoft commented 4 months ago

Fastlane changelogs are limited to 500 chars (and are truncated at that point, even if it's mid-word). However, yours are more than twice as large:

! metadata/de.mm20.launcher2.release/en-US/changelogs/2024050700.txt has 1114 chars
! metadata/de.mm20.launcher2.release/en-US/changelogs/2024050900.txt has 1114 chars
! metadata/de.mm20.launcher2.release/en-US/changelogs/2024051000.txt has 1114 chars

image

Curious why the size was exactly identical: well, so was the content. I guess you're not repeating the same changes with each release, are you? :zany_face:

MM2-0 commented 4 months ago

Fastlane changelogs are limited to 500 chars

Meh. Okay, thanks, I will keep that in mind. So the best practice would be to link to the Github release for the full changelog?

Curious why the size was exactly identical: well, so was the content. I guess you're not repeating the same changes with each release, are you?

I copy the changelog of the previous feature update when I need to release a bugfix update before the F-Droid main repo caught up to the previous feature update. Most of the time, bugfix updates fix bugs that were introduced in the previous feature update, so they aren't relevant to users who never used that version. New features on the other hand are way more exciting and I don't want anyone to miss out on anything.

IzzySoft commented 4 months ago

So the best practice would be to link to the Github release for the full changelog?

I'd point out the most important changes in fastlane, ending with something like "for details and a full list, see {link-to-releases}", or link to a full Changelog.md if you have such, yeah. Then you have the best of two worlds. Breaking changes and important updates (what one needs to know before updating) definitely in the fastlane per-release changelogs, as those are usually shown next to the app description with the F-Droid clients (and in my repo browser as well).

before the F-Droid main repo caught up to the previous feature update

Eh, that usually takes around 5 days, yeah. At IzzyOnDroid it's max 24h usually. Thanks, that explains! And yeah, we won't rob those using F-Droid.org from those details, right.