- Boost - lists.boost.org

async-mqtt5 is CONDITIONALLY ACCEPTED
by Klemens Morgenstern 09 Nov '24

09 Nov '24

Hi all, thanks to everyone participating in the review! I really want to express my appreciation to the reviewers, especially those who invested multiple hours if not days to review this library: thank you Vinnie, Ruben, Mohammad and Marcelo. I interpreted Darylls review as a "weak rejection", but since that doesn't exist in the formal review process I'll count it as a rejection. Leaving the recommendations at 1 ACCEPT 3 CONDITIONAL ACCEPT 2 REJECT The actual conditions for acceptance are: 1. Correct usage of the executor. It is an asio contract that the async operation always completes on the associated executor and mqtt5 should follow this. 2. Add logging/reporting facilities. A user should be able to follow what is happening internally and ideally react to it, especially concerning reconnects. I also recommend the authors to review all the comments, including the rejections (Daryll's review had interesting details) and non-review comments such as from Peter Turcan. I would also advise that inclusion in boost is usually a time to change the name, because the library now gains the boost. prefix. I.e. boost.async-mqtt5 might be a bit cumbersome. Also note that there is no time requirement to include this library in boost in the next release. Thanks again to everyone participating in the review and to Ivica & Mireo for their submission.

15 47

Slack and Formal Reviews
by Vinnie Falco 09 Nov '24

09 Nov '24

We need to solve the problem of review conversations taking place on Slack instead of the list. I would ultimately love a technical solution that allows discussions to also happen on Slack in a way that preserves the integrity of the review, and that might not be practical right this second. Therefore, I propose the following: 1. Formal review announcement will remind participants that conversations should happen on the list (and specifically mention that Slack should not be used) 2. If a Slack conversation is initiated during the review period, the review manager and library submitter will politely remind folks to move the discussion to the list. Perhaps some copy and pasting will be needed. 3. Periodic reminder from the review manager during the review process, if things get out of hand. 4. We explore ideas for how to incorporate other platforms into the review process. Mailing list participation is down, yet Slack participation is up. Ideally we figure out how to harness change instead of taking on losing battles. -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

1 0

Shared memory path to custom path
by Murali Kishore 08 Nov '24

08 Nov '24

Hi all, Is it possible to change the shared memory segment path from /dev/shm to other directory ex. /tmp/shm_file instead of /dev/shm/shm_file. Regards, Murali Kishore

3 4

[release] Boost 1.87.0 Beta 1 Release Candidate is available
by Marshall Clow 08 Nov '24

08 Nov '24

Available at: https://archives.boost.io/beta/1.87.0.beta1/source/ The SHA256 checksums are as follows: 26f987635320854a141a8c9c3750eb6f01edb6eb75df9454726c4a03724b2472 boost_1_87_0_b1_rc1.tar.gz 3712ead87a26ae5b8ee7dcf0c180e4c27f58e50bd32f14d77e8e04bf6a13ae51 boost_1_87_0_b1_rc1.zip e6b047e06369392241f8574a5cc1b6aa493819aa498276654477e3a08bc94167 boost_1_87_0_b1_rc1.7z deff255d96e11760f728f5f90785b138fff93f6c9a3ab24664710211a41614ad boost_1_87_0_b1_rc1.tar.bz2 As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Release Managers

4 6

[Release] Master branch is now closed for the beta release
by Marshall Clow 07 Nov '24

07 Nov '24

Master is closed for all changes. See the release schedule at: https://www.boost.org/development/index.html -- Release managers

1 0

[release] Master branch closes for the 1.87.0 beta release on WEDNESDAY
by Ion Gaztañaga 05 Nov '24

05 Nov '24

Calendar is here: https://www.boost.org/development/ — The Release Managers

1 0

Bringing Boost.Array up to date?
by Peter Dimov 05 Nov '24

05 Nov '24

I recently needed to make use of std::array in a constexpr context, and was rudely informed by the compilers that a lot of its features are only constexpr in C++17 (non-const access) or even C++20 (operator==). This makes the standard std::array not very useful in C++14 constexpr code. Ordinarily, the way we deal with such problems is to shadow the standard component in Boost.Compat and backport all features introduced in later standards. But in this specific case, we already have boost::array, and it makes no sense to introduce another one. boost::array, however, looks mostly abandoned. The thinking there was probably that it's rendered entirely obsolete by std::array, and that no further development is warranted or required. But as outlined above, this is not the case; there's still value in maintaining boost::array and keeping it up to date. I'd like to do something about that. If Array's current maintainer, Marshall, agrees, I'd like to take over the maintenance of Boost.Array and do the usual thing - port the documentation to AsciiDoc, expand the test suite, add the necessary BOOST_CONSTEXPR/BOOST_CXX14_CONSTEXPR annotations, add the features introduced by later standards such as deduction guides and to_array, deprecate/remove the nonstandard parts of boost::array that are no longer relevant in 2024, and so on. Comments?

2 1

[release] The 1.87.0 release will close for major changes WEDNESDAY
by Ion Gaztañaga 05 Nov '24

05 Nov '24

Calendar here: https://www.boost.org/development/ Next deadline: The master branch will close for the beta next Wednesday. — The release managers

4 4

[async-mqtt5] Formal review starts today
by Klemens Morgenstern 28 Oct '24

28 Oct '24

Hi all, the formal boost review of the async-mqtt5 library strats today, the 16th of October and will last until and including the 25th of this month. Async.MQTT5 is a professional, industrial-grade C++17 client built on Boost.Asio. This Client is designed for publishing or receiving messages from an MQTT 5.0 compatible Broker. Async.MQTT5 represents a comprehensive implementation of the MQTT 5.0 protocol standard, offering full support for publishing or receiving messages with QoS 0, 1, and 2. The library has been developed by mireo, a GPS/GIS software development company, and their CTO Ivica Siladić submitted it. The code under review is the current master, which is tagged as v1.0.2: https://github.com/mireo/async-mqtt5/releases/tag/v1.0.2 The documentation can be found here: https://spacetime.mireo.com/async-mqtt5/ Please explicitly state that you either *accept* or *reject* the inclusion of this library into boost. Also please indicate the time & effort spent on the evaluation and give the reasons for your decision. - Does this library bring real benefit to C++ developers for real world use-case? - Do you have an application for this library? - Does the API match with current best practices? - Is the documentation helpful and clear? - Did you try to use it? What problems or surprises did you encounter? - What is your evaluation of the implementation? - Do you have experience with asio? - Did you work with MQTT in the past? More information about the Boost Formal Review Process can be found at: http://www.boost.org/community/reviews.html The review is open to anyone who is prepared to put in the work of evaluating and reviewing the library. Prior experience in contributing to Boost reviews is not a requirement. Reviews can also be submitted privately to me, and I will not disclose who sent them. I might however cite passages from those reviews in my conclusion. I think I should mention that there's another mqtt library that has been proposed for boost, but has yet to find a review manager: https://github.com/redboltz/async_mqtt Some ideas of how we could review them together have been discussed on the mailing list, but this is an independent review of mireo's async-mqtt5. You don't have to consider redboltz/async_mqtt when writing your review. Thanks to Mireo & Ivica for submitting this library.

8 17

[async-mqtt5] Review ends tomorrow
by Klemens Morgenstern 27 Oct '24

27 Oct '24

Reminder: the review period for async-mqtt5 will end tomorrow on Monday the 28th. Thanks for all the great reviews received so far!

1 0