Monday 13th March 2017: 6.11pm. Link shared: https://www.reddit.com/r/cpp/comments/5z5r5i/boostoutcome_is_finished_boost_review_manager/?ref=share&ref_source=link One of those big ol personally momentus days today. In the wee small hours last night shivering in Clara's bedroom as I'd stayed there working on the laptop after putting her to bed and it got cold, I finally delivered my Outcome library to Boost peer review. That library has taken me two years of my free time to write, and a never ending long tail of incredibly boring minute detail over the past four months or so to actually deliver the thing. ...
Saturday 3rd June 2017: 9.45pm. The peer review of my proposed Boost.Outcome library ended yesterday after being extended to two weeks to allow more discussion. Some 732 emails were sent on the topic, one of the most vigorous debates on boost-dev in many years, and a very highly productive one I think despite that we did not find consensus.#boostcpp #c++ #boost-outcome
...
Wednesday 7th June 2017: 8.24am. Link shared: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html My proposed Boost.Outcome library's review report: http://boost.2283326.n4.nabble.com/review-Outcome-Review-Report-tt4695267.html. It was rejected after one of the lengthiest reviews in many years. Lots of good feedback on how it ought to look. #boostcpp #c++ #boost-outcome
...
Thursday 18th January 2018: 9.40pm. Link shared: https://github.com/ned14/outcome/releases/tag/v2.0-boost-peer-review My third Boost peer review begins tomorrow, and lasts ten days. Let's hope that this time I succeed, only been at this since 2012, and the proposed C++ library only since 2014!#boost-outcome #boostcpp #cpp
...
Monday 5th February 2018: 9.52am. Link shared: http://boost.2283326.n4.nabble.com/review-Boost-Outcome-v2-Review-Report-td4701728.html #boostoutcome#boost-outcome#boostcppOutcome is accepted into Boost, and http://boost.2283326.n4.nabble.com/review-Boost-Outcome-v2-Review-Report-td4701728.html links to the review manager's report (be warned, it is lengthy). Here is what I wrote in acknowledgement:I'd like to thank Charley for writing such a lengthy and detailed review report, in addition to performing duties in one of the hardest review managements I think I've seen this decade.I'd like to thank the reviewers for their feedback, and all those who have written me emails and sent me their notes and pull requests. ...
Contact the webmaster: Niall Douglas @ webmaster2<at symbol>nedprod.com
(Last updated: 2018-02-05 09:52:54 +0000 UTC)