I would like to ask FESCo to review this Change proposal:
This change brings Boost 1.64.0 to Fedora 27. This will mean F27 ships with a recent upstream Boost release.
Metadata Update from @jkurik: - Issue tagged with: meeting
+1
@jwakely The contingency plan on the change proposal page is copied unchanged from the F26 change:
Contingency Plan Contingency mechanism: Worst case scenario is to abandon the update and simply ship F26 with Boost 1.60, which is already in rawhide. If 1.63 (or 1.64) causes too many problems for clients being rebuilt then it might be possible to use 1.62 or 1.61 instead, which would still be an improvement over F24 and F25. Contingency deadline: We will know whether the change can be made once the rebuilds in the side tag are done, which is likely to be some time in January 2017. Blocks release? No Blocks product? None
Contingency Plan
Contingency mechanism: Worst case scenario is to abandon the update and simply ship F26 with Boost 1.60, which is already in rawhide. If 1.63 (or 1.64) causes too many problems for clients being rebuilt then it might be possible to use 1.62 or 1.61 instead, which would still be an improvement over F24 and F25.
Contingency deadline: We will know whether the change can be made once the rebuilds in the side tag are done, which is likely to be some time in January 2017.
Blocks release? No Blocks product? None
Please update it for F27.
+1 once that's fixed.
Oops, fixed, thanks.
I took the liberty and corrected the copy&paste typo in the Release Notes section, but please verify.
Thanks.
Metadata Update from @jforbes: - Issue untagged with: meeting - Issue status updated to: Closed (was: Open)
So is this now approved? Will https://fedoraproject.org/wiki/Changes/F27Boost164 be updated, or can I request the side tag via https://pagure.io/releng/issue/6851 without waiting for the wiki update?
I don't have much time to do the rebuilds, since a mass rebuild is scheduled very soon.
@jwakely The wiki page is now updated. I am sorry for the delay in updating the status, it was caused by my long PTO.
Login to comment on this ticket.