List view
The next release when functionality is added in a backward compatible manner
Due by April 11, 2025•180/180 issues closedThe next release when backwards compatible bug fixes are made
Due by November 28, 2023•88/88 issues closedThe next release when backwards compatible bug fixes are made
Due by August 12, 2022•33/33 issues closedThe next release when backwards compatible bug fixes are made
Due by August 1, 2022•3/3 issues closedThe next release when functionality is added in a backwards-compatible manner.
Due by August 1, 2022•144/144 issues closedThe next release when backwards compatible bug fixes are made
Due by January 3, 2022•29/29 issues closedThe next release when backwards compatible bug fixes are made
Due by October 16, 2021•6/6 issues closedThe next release when backwards compatible bug fixes are made
Due by October 8, 2021•12/12 issues closedThe next release when backwards compatible bug fixes are made
Due by August 26, 2021•3/3 issues closedThe next release when backwards compatible bug fixes are made
Due by August 24, 2021•18/18 issues closedThe next release when functionality is added in a backwards-compatible manner.
Due by August 17, 2021•117/117 issues closedThe next release when backwards compatible bug fixes are made
Due by August 6, 2020•11/11 issues closedThe next release when functionality is added in a backwards-compatible manner
Due by July 27, 2020•73/73 issues closedThe next release when functionality is added in a backwards-compatible manner
Due by June 14, 2020•119/119 issues closedThe next release when backwards compatible bug fixes are made
Due by November 17, 2019•2/2 issues closedThe next release when backwards compatible bug fixes are made
Due by November 10, 2019•5/5 issues closedThe next release when backwards compatible bug fixes are made
Due by November 6, 2019•27/27 issues closedThe next release when backwards compatible bug fixes are made
No due dateThe next release when backwards compatible bug fixes are made
Due by March 20, 2019•3/3 issues closedThe next release when functionality is added in a backwards-compatible manner
No due date•24/24 issues closedThe next release when functionality is added in a backwards-compatible manner
Due by March 20, 2019•43/43 issues closedThe next release when functionality is added in a backwards-compatible manner
Due by December 22, 2018•16/16 issues closedThe next release when functionality is added in a backwards-compatible manner
Due by October 30, 2018•19/19 issues closedThe next release when backwards compatible features are introduced to the public API
Due by October 5, 2018•29/29 issues closedThe next release when backwards compatible features are introduced to the public API
Due by August 20, 2018•41/41 issues closedThe next release when backwards compatible bug fixes are made
Due by March 14, 2018•8/8 issues closedThe next release when backwards compatible bux fixes are made
Due by February 13, 2018•9/9 issues closedThe next release when backwards compatible features are introduced to the public API
Due by February 1, 2018•31/31 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by February 25, 2017•19/19 issues closedThe next release when backwards compatible bux fixes are made
Due by December 29, 2017•7/7 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by January 2, 2017•11/11 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by December 16, 2016•11/11 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by December 2, 2016•5/5 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by November 2, 2016•3/3 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by October 15, 2016•7/7 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by September 14, 2016•1/1 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by September 11, 2016•2/2 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by August 31, 2016•4/4 issues closedThe next release if backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Due by July 30, 2016•5/5 issues closedBugfix release due to #272.
No due date•1/1 issues closedThe next release when backwards incompatible changes are introduced to the public API
Due by December 17, 2017•130/130 issues closedThe next release if new, backwards compatible functionality is introduced to the public API
Due by January 28, 2017•10/10 issues closedThis release adds several features such as JSON Pointers, JSON Patch, or support for 64 bit unsigned integers. Furthermore, several (subtle) bugs have been fixed. As `noexcept` and `constexpr` specifier have been added to several functions, the public API has effectively been changed in a (potential) non-backwards compatible manner. As we adhere to [Semantic Versioning](http://semver.org), this calls for a new major version, so say hello to 2️⃣.0️⃣.0️⃣.
Due by June 23, 2016•34/34 issues closed- Due by January 23, 2016•19/19 issues closed
The 1.0.0 release should be the first "official" release after the initial announcement of the class in January 2015 via reddit ("0.1.0") and a heavily overworked second version ("0.2.0") in February. By switching to official releases, I would like to make the class evolution and feature set more predictable. The times of frequent API changes are over. This milestone collects issues that should be finished before a release can be made.
No due date•5/5 issues closed