I am re-sending this Change announcement to the devel@ list, as due to the migration of mailinglists the original announcement [1] has reached only devel-announce@ mailing list and has never been forwarded to the devel@ list. [1] https://lists.fedoraproject.org/archives/list/devel-announce%40lists.fedoraproject.org/thread/7I6QJPJLXO4X6J24NORV2OR44UE5VBVS/ Regards, Jan On Fri, Nov 27, 2015 at 9:24 AM, Jan Kurik <jkurik@xxxxxxxxxx> wrote: > = System Wide Change: Fedora 24 Boost 1.60 uplift = > https://fedoraproject.org/wiki/Changes/F24Boost160 > > Change owner(s): > * Jonathan Wakely < jwakely AT redhat DOT com > > > This change brings Boost 1.60.0 to Fedora 24. This will mean F24 ships > with the latest upstream Boost release. > > == Detailed Description == > The aim is to synchronize Fedora with the most recent Boost release. > Because ABI stability is one of explicit Boost non-goals, this entails > rebuilding of all dependent packages. This has also always entailed > yours truly assisting maintainers of client packages in decoding > cryptic boostese seen in output from g++. Such care is to be expected > this time around as well. > > Boost 1.60 is scheduled for release on 2 Dec 2015 and a beta release > is already available for testing > > The equivalent changes for previous releases were Fedora 22 Change and > Fedora 23 Change. > > > == Scope == > > Proposal owners: > * Build will be done with Boost.Build v2 (which is upstream-sanctioned > way of building Boost) > * Request a "f24-boost" build system tag (discussion): > https://fedorahosted.org/rel-eng/ticket/6235 → f24-boost > * Build boost into that tag (take a look at the build #606493 for inspiration) > * Post a request for rebuilds to fedora-devel (XXX link to > fedora-devel message here) > * Work on rebuilding dependent packages in the tag. > * When most is done, re-tag all the packages to rawhide > * Watch fedora-devel and assist in rebuilding broken Boost clients (by > fixing the client, or Boost). > > In order to discover any problems ASAP the proposal owner has created > a COPR and built the Boost 1.60.0 beta, and started rebuilding the > 300+ dependent packages. The results of this COPR will be thrown away, > but it means any bugs in the upstream release can be reported and > fixed before the final release (rather than patched in the Fedora > package) and any changes needed in dependent packages will be known > sooner. > > Other developers: > Those who depend on Boost DSOs will have to rebuild their packages. > Feature owners will alleviate some of this work as indicated above, > and will assist those whose packages fail to build in debugging them. > The proposal owner has already started test rebuilds of affected > packages and identifying the needed changes, and will propose patches > to Boost upstream or to the client packages' upstreams as appropriate. > > Release engineering: > * Side tag creation. > > List of deliverables: > * All deliverables will include updated Boost packages > > Policies and guidelines: > * Apart from scope, this is business as usual, so no policies, no guidelines. > > Trademark approval: > * N/A (not needed for this Change) > > > -- > Jan Kuřík > Platform & Fedora Program Manager > Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic -- Jan Kuřík Platform & Fedora Program Manager Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
