-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Fastlane changelogs have oversize #849
Comments
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?
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. |
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
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. |
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:
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? 🤪
The text was updated successfully, but these errors were encountered: