Martin Kolman wrote:
> But even for package development and integration you need something that
> works at least a bit. If you won't get a compose for a few weeks due to
> the constant breakage you won't get much work done on landing your latest
> library rebase or integrating a new package.
In the past, the compose would not fail just because a release-blocking
deliverable failed to compose, the package compose would just ship without
the deliverables that failed to compose. That's what needs to happen again.
There is no technical reason why an error composing a live ISO prevents the
changed RPMs from going out. Rawhide is not a release, there should be time
until the actual release to fix the release-blocking deliverable.
And ideally, we would keep the last successful compose of each deliverable
on the mirrors, no matter whether it matches the current package compose or
not. (We did not do that in the past, the ISO was just missing when the
latest version failed to compose, which is suboptimal.)
We need to stop having unreasonable expectations about Rawhide's quality,
and ISOs always composing successfully is one such unreasonable expectation.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
