Does anyone need to delay the 2.47 release ?
A build failure in generated files might delay the binutils 2.47 release.
Jan Beulich raised a concern about a build failure in generated files potentially delaying the upcoming binutils 2.47 release. Nick Clifton is seeking confirmation if applying a specific fix is sufficient or if other issues necessitate a postponement. Alice Carlotti acknowledged the fix and apologized for the breakage.
- proposer
Asked whether a build failure in generated files should delay the binutils 2.47 release, noting that such failures are undesirable in release trees, yet generated files usually don't require regeneration for releases.
“Question is whether the build failure addressed by [1] is enough of a reason to delay. Generally generated files shouldn't need re-generation in release trees, and hence the tools to generate such files shouldn't need building in the first place. Yet otoh having such a build failure in a release also isn't very nice.”
- maintainer
Inquired if the proposed patch is sufficient to resolve the build failure or if further action is needed before the 2.47 release.
“Is applying [1] a sufficient solution to this problem or are there other build”
- contributor
Acknowledged the proposed solution and apologized for causing issues with the build.
“OK, thanks - and apologies again for the breakage.”
Technical Tradeoffs
- Delaying the release to fix a build issue versus releasing on time with a potential minor defect.
- Ensuring release stability versus adhering to a fixed release schedule.
In Details
This discussion concerns the binutils 2.47 release timeline. Jan Beulich identified a build failure related to generated files in the release branch. The core issue is whether this failure, and the fix proposed in [1], warrants delaying the release, as generated files and their build tools are typically not part of release artifacts.