This is a tracking bug for Change: Fedora 22 Boost 1.58 Uplift
For more details, see: https://fedoraproject.org//wiki/Changes/F22Boost158
This change brings Boost 1.57.0 or later to Fedora 22. We generally aim to ship 1.58.0, as that seems likely to make it (hence the Change name), but 1.57.0 is out and available now.
This message is a reminder that Fedora 22 Change Checkpoint: Completion deadline (testable) is on 2015-02-24 .
At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.
This bug should be set at least to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. Fedora 22 is going to be strictly time based release. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon.
In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you.
This message is a reminder that Fedora 22 "Change Checkpoint: 100% Code Complete Deadline" is on 2015-03-31 .
All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA.
As for several System Wide Changes, Beta Freeze is a point of contingency plan, all incomplete Changes will be reported to FESCo for 2015-04-01 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik).
Hi Petr, we would like to include this change in F22 Beta Release Notes. Could you please tell me which version of Boost will be available in F22 Beta? The Change page mentions both 1.57 and 1.58.
Boost 1.57.0 is the one we ship in F22.
I wrote a draft release note; please take a look at the text in the Doc Text field and let me know if it's sufficient, or if there's anything you'd like to add or change.
I would recommend rebuilding all the clients. The ones that use DSO's will of course not even start, but even those that don't, may hit ABI changes if they interface with third-party code that uses Boost types across API boundary.
Changed the second paragraph. Is it OK now?
Yep, good stuff. Thanks!