Closure of Older Issues in Failed-Compose Tracker
by Samyak Jain
Hello, folks 0/
I hope this email finds you well. I am writing to inform you about an
upcoming action regarding the failed-compose tracker list.
As some of you may be aware, several older issues remain open in the
failed-compose tracker. These issues have been inactive for some time
and their closure has become necessary to streamline our operations
and reduce clutter. Therefore, I will be closing these older issues
tomorrow. This action may trigger a significant number of emails for
each closed issue. I have explored various options to disable these
notifications, both within the pagure settings for the repository and
through the pagure API, but unfortunately, no viable workaround has
been found.
To minimize any inconvenience caused by this email flood, I wanted to
provide advance notice to subscribers of the failed-compose tracker
list. Please note that this process of closing older issues will be
conducted post every release cycle onwards to ensure the efficiency of
our tracking system.
The script to close these older issues will likely be triggered around
8:00 UTC tomorrow. You can find more information about the
failed-compose tracker and its issues on the following link:
https://pagure.io/releng/failed-composes/
If you have any concerns or suggestions regarding this matter, please
feel free to reach out to me directly or reply here.
Thank you for your understanding and cooperation.
Best regards,
Samyak Jain
Fedora Release Engineering
1 week
Renaming distribution media for Fedora Server
by John W. Himpel
The Fedora Server WG is seriously contemplating changing the naming
convention for its distribution media.
We have developed a naming convention that we would like to follow.
It can be found at: https://pagure.io/fedora-server/issue/126
As we began our research in preparation of s system-wide change
proposal, we discovered two things:
1) The current naming convention has it's tentacles far and wide
thought the distribution generation processes, distribution processes
and documentation.
2) The Fedora Server WG recognizes quite clearly that "we don't know
what we don't know".
We are hopeful the Release Engineering team will assist in the early
stages of acquiring the necessary knowledge to develop a cogent and
complete system-wide change. Firstly, we need help in identifying all
the areas within Fedora Project that would require change. Secondly,
we need help in developing a detailed statement of work for each of the
areas requiring change.
We would greatly appreciate if the Release Engineering team would
assign someone from the team to work with us and serve a "guide" for us
as we attempt to complete the two above objectives.
I have been appointed as the point of contact for this effort.
We look forward to engaging with the Release Engineering team for this
effort.
1 week, 1 day