[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: Appstream BoF notes
From:       Ben Cooksley <bcooksley () kde ! org>
Date:       2021-06-24 19:08:48
Message-ID: CA+XidOHmP5aqpKsTmr77j2vvtN-kXZKPrRguOGFaG3KhkKWJnw () mail ! gmail ! com
[Download RAW message or body]

On Thu, Jun 24, 2021 at 11:50 PM Jonathan Riddell <jr@jriddell.org> 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

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">On Thu, Jun 24, 2021 at 11:50 PM Jonathan Riddell \
&lt;<a href="mailto:jr@jriddell.org">jr@jriddell.org</a>&gt; wrote:<br></div><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
id="gmail-m_1500611857863246804gmail-magicdomid15"><span>        </span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid16"><span>Appstream BoF \
notes<br></span></div><div id="gmail-m_1500611857863246804gmail-magicdomid17"><span>  \
- metadata updater rewrite should be its own repo so as not to break uses of existing \
code</span></div></div></blockquote><div><br></div><div>Is there a plan to list all \
existing users of the code and migrate them to the new rewrite?</div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div \
id="gmail-m_1500611857863246804gmail-magicdomid18"><span>  - the rewrite should get \
tests to prove it works</span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid181"><span>  - much of this must be a \
solved problem, aren&#39;t appstream or other users creating scripts that do these \
features?</span><span> ideally it would go upstream to appstream.</span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid20"><div \
id="gmail-m_1500611857863246804gmail-magicdomid24"><span>     </span><span>- \
appstreamcli has news-to-appstream converter and appstream-util has similar, probably \
not very useful as we don&#39;t use news files </span><span><a \
href="https://blog.tenstral.net/2020/03/maintain-release-info-easily-in-metainfo-files.html" \
rel="noreferrer noopener" \
target="_blank"><u>https://blog.tenstral.net/2020/03/maintain-release-info-easily-in-metainfo-files.html</u></a></span></div><span> \
- should changelogs be translateable?    </span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid21"><span>       - possibly yes, \
shouldn&#39;t be super hard to support in scripty</span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid22"><span>  - &quot;Date in iso \
standard e.g 04-03-2022&quot; is not ISO format</span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid23"><span>  - Links to artifacts could \
be generated  </span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid34"><span>  - release time checks \
prior to publishing tars?</span><span> ideally.</span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid58"><span>  - checks done in neon at \
</span><span><a href="https://metadata.neon.kde.org/appstream/user_focal/html/focal/main/issues/index.html" \
rel="noreferrer noopener" \
target="_blank">https://metadata.neon.kde.org/appstream/user_focal/html/focal/main/issues/index.html</a></span></div><div \
id="gmail-m_1500611857863246804gmail-magicdomid214"><span>  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</span></div><div><span><br></span></div></div></blockquote><div><br></div><div>Cheers,</div><div>Ben \
</div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]