There are a few possibilities. One is that we try to force an update to 4.2 no matter when it's released, trying to push it into yakkety even after release-day. The rationale would be that the snapshot is anyway closer to 4.2 than anything, so it would be more like a 'bugfix' than a new feature-release. All features planned for 4.2 are already in so there should be no surprises here. We can of course also track the development of 4.2 and cherry-pick important fixes to our snapshot release, but I would really like to switch to 4.2 as soon as possible.
4.2 introduces no ABI breakages (at least not any obvious ones looking at the symbol files), so any step here should be relatively convenient as no rebuilds are needed (instead of zmqpp of course). It's backward compatible API-wise. Another possibility would be, of course, simply pushing a fork of zeromq3 to the archives that would be snapshot-based. This would mean we'd stay on 4.1.5 on yakkety for zeromq3 but some separate package, like, zeromq3-future (wrong name, but just an example) would provide the snapshot-based binaries instead. This way we would only have zmqpp as the consumer (and the only consumer of zmqpp is unity-scopes-api). This is much safer but very ugly from the archive perspective - but maybe this could be thought of as a better solution? It's also tough for me as this is the first situation like this we have to deal with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612240 Title: [FFe] Please upgrade zeromq3 and zmqpp to 4.1.2 git snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1612240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
