rapidjson
rapidjson copied to clipboard
Tencent
Time for the next release?
I see it has been a while since 1.1 was released. Should the next release happen soon?
I think we should release a minor version, may be v1.1.1, ideally after several known bugs resolved.
I am also planning of some future development, such as a new DOM API for C++11/14, and further performance optimization. But timing is uncertain. I hope we can discuss them openly in the community.
"ideally after several known bugs resolved" Are these bugs in 1.1? Or are you talking about new bugs?
https://github.com/miloyip/rapidjson/issues?q=is%3Aopen+is%3Aissue+label%3Abug
Any word on when we'll get a new release? I'm looking at upgrading, but will hold off if there's a new version coming out soon.
I would vote for a point release as well, and then accepting that there are known bugs for that release. The last actual release dates more than a year now.
@miloyip I'm confused why you think the software needs to be bug free to label a new release? No software would ever be released if that were the case.
A concrete example of how this is negatively affecting users is as follows: In a VS2017 environment I am using vcpkg to install rapidjson. It installs 1.1. That not only means that I'm not getting the benefits of the last 355+ commits, but also it is not compatible with C++17 in Visual Studio. So the default workflow to use this library for a lot of people results in immediate error's during build.
The result is a lot of lost productivity tracking down the problem, and then a set of workarounds to get this library from master, whereas other libraries are being pulled from vcpkg.
You and the community have done an awesome job with this library, and I thank you. Please share these updates with the world with a v1.2 or v1.1.1 release!
@emusgrave Not to dissuade the owners from releasing earlier and often-er, but you can install master (if desired) by running vcpkg install rapidjson --head.
@ras0219-msft vcpkg install rapidjson --head fails for this project. I'm still trying to figure out how to fix it.
Someone else may need to prepare a full release (updating files with new versions, dependencies, etc) and submit it as a pull request before a release happens; it might be that there's just no time to do it. Unless there's some active resistance to releasing?
Soon it will be 4 years since the last release. any chance a new release might happen or is this project dead?
Indeed, 4 years, 500+ commits...
@miloyip any reasons for having so much resistance on new releases? As mentioned before, everyone understands that software cannot be bug-free, it will never be "perfect", and it's perfectly fine. I'm sure from 2016 there were already some solid improvements done (in other case there would be no commits in master any more). Could you please share the reasons why isn't it still available for wide public (==using official releases)?
Agree with @okainov 's comment, IMHO it is good to do releases bases on already fixed bugs and added features then trying to clear all reported bugs, though the later is noble, but not always the highest priority. I think 550 commits is worth trying to summarize in a highly anticipated release.
+1 for a new release. Lots of bugs have already been fixed, but no one downloading the latest stable release will get them. I'm kindly asking for a new version that I can refer to.
Not to complain, just to point out that the last release 1.1.0 doesn't seem to compile with the most recent LTS version of Ubuntu: 20.04 ...
While a new release is still pending, I would love to see a due date (goal) assigned to the v1.2 Beta Milestone.
The only result you get with NOT releasing, is that everyone will just use master. So basically every commit you do is a release now..
A new release would be nice. Could the community get some feedback on this please?
Will there ever be a new release? Most of developer can not trust and use just a commit state from master, if maintenance does not change to better, this API will be useless for real SW products.
Duplicate are #1919 #1006 #1130 #1341 #1896 #1911
@miloyip rapidjson is really a very wonderfull library
I had to migrate from current release to a "last git" version for c++17 compatibility issues.
A lot of people think a new release with current code is needed !!
@miloyip I'm confused why you think the software needs to be bug free to label a new release? No software would ever be released if that were the case.
You and the community have done an awesome job with this library, and I thank you. Please share these updates with the world with a v1.2 or v1.1.1 release!
I think also we can release a software with opened bug. We only must be carreful thant new version don't introduce new bug
A new release would be VERY appreciated! Lots of new features added since 1.1.0 are what I need!
Since OG rapidjson doesn't do releases anymore, does anyone have a specific fork that keeps up on handling and maintaining releases?
Since OG rapidjson doesn't do releases anymore, does anyone have a specific fork that keeps up on handling and maintaining releases?
Use nlohmann C++ json lib, it is much better in releasing and documentation. I gave up waiting for new rapidjson release, i am using this other from now. https://github.com/nlohmann/json
