On Thu, Jun 24, 2021 at 11:50 PM Jonathan Riddell <[email protected]> wrote:
> > Appstream BoF notes > - metadata updater rewrite should be its own repo so as not to break uses > of existing code > Is there a plan to list all existing users of the code and migrate them to the new rewrite? > - the rewrite should get tests to prove it works > - much of this must be a solved problem, aren't appstream or other users > creating scripts that do these features? ideally it would go upstream to > appstream. > - appstreamcli has news-to-appstream converter and appstream-util has > similar, probably not very useful as we don't use news files > *https://blog.tenstral.net/2020/03/maintain-release-info-easily-in-metainfo-files.html* > <https://blog.tenstral.net/2020/03/maintain-release-info-easily-in-metainfo-files.html> > - should changelogs be translateable? > - possibly yes, shouldn't be super hard to support in scripty > - "Date in iso standard e.g 04-03-2022" is not ISO format > - Links to artifacts could be generated > - release time checks prior to publishing tars? ideally. > - checks done in neon at > https://metadata.neon.kde.org/appstream/user_focal/html/focal/main/issues/index.html > Actions: carl to close MR, put it in own repo (with a nice sounding name) > or release-tools repo or releaseme, update scripty to make changelogs > translateable > > Cheers, Ben
