thunderbird-website icon indicating copy to clipboard operation
thunderbird-website copied to clipboard

Thunderbird for Android Release Notes

Open Sancus opened this issue 1 year ago • 7 comments

We should get this figured out. Is there interest in using the same structure as https://github.com/thunderbird/thunderbird-notes ? That would be the easiest for publishing on the website.

We can publish to different URLs or pages, change page layouts, etc. We could use a different repo or the same repo but a different folder. Lots of options here. Only caveat is I'd be careful about forking the whole thing and changing the logic, as then we have two notes libraries that need to be maintained.

Sancus avatar Sep 26 '24 18:09 Sancus

Tangential, https://github.com/thunderbird/thunderbird-notes/issues/43 suggests changes needed to the links in desktop release notes. These same 3 links will need to be changed for android release notes.

wsmwk avatar Sep 29 '24 17:09 wsmwk

It's now in thunderbird-notes https://github.com/thunderbird/thunderbird-notes/blob/master/android_release/8.0.yml

But we don't have any version information to actually list in on a page without crawling the directory.

MelissaAutumn avatar Nov 05 '24 18:11 MelissaAutumn

Corey did point out we could parse it from github directly, if we assume either the name or tag scheme doesn't change then we should be able to line it up with the yml information.

https://api.github.com/repos/thunderbird/thunderbird-android/releases

MelissaAutumn avatar Nov 05 '24 18:11 MelissaAutumn

It's worth noting the structure of the TfA yaml files in https://github.com/thunderbird/thunderbird-notes have differences vs the desktop yaml files. These differences need to be documented in the README. I will try to get to that soon.

coreycb avatar Nov 05 '24 19:11 coreycb

The code that parses the notes is all in thunderbird-notes. I suggest that the notes should be normalized in terms of format, so the same type of property always has the same name in any notes file regardless of product.

Any changes to the baseline spec should be added as features/new properties that would also work in any notes file. If an old property needs to be restructured to accommodate a new requirement, you can always do a migration script. We've done that before.

Maintaining distinct structural differences for each new app that gets added is probably not sustainable.

Sancus avatar Nov 05 '24 21:11 Sancus

Hey @coreycb were those differences ever documented?

MelissaAutumn avatar May 21 '25 17:05 MelissaAutumn

@MelissaAutumn They aren't. I'll prioritize that.

coreycb avatar May 21 '25 18:05 coreycb