Le sam. 8 oct. 2022 à 17:06, sebb a écrit :
>
> Some recent changes files include details of updates to GitHub actions
> in workflows.
>
> I don't think these details belong in the changes file.
> They are not relevant to the release.
>
> Indeed the workflows that contain the updates are not inclu
Le 08/10/2022 à 17:56, sebb a écrit :
I don't think we should be cluttering the changes file with irrelevant
and potentially confusing information.
+1, changes.xml should be for user visible changes only (API changes,
bug fixes, updated language level, etc).
Emmanuel Bourg
On Sat, 8 Oct 2022 at 16:22, Gary Gregory wrote:
>
> Sebb,
>
> The idea behind describing these changes is to provide a transparent
> account of how we build the software and using a CI system is critical to
That sort of information belongs on the website (if anywhere), not in
the release.
It's c
Sebb,
The idea behind describing these changes is to provide a transparent
account of how we build the software and using a CI system is critical to
our overall efforts IMO. If you don't want to update a changes.xml file
then don't.
Gary
On Sat, Oct 8, 2022, 11:06 sebb wrote:
> Some recent cha
Some recent changes files include details of updates to GitHub actions
in workflows.
I don't think these details belong in the changes file.
They are not relevant to the release.
Indeed the workflows that contain the updates are not included in the
release -- nor should they be.
Sebb
--
