Hello,
>Great! please check and close the various RC bugs to let this one migrate :) >Beware, for 3.12.0, you need to change the source package name too, not just >the binares, >otherwise nlohmann-json3 3.11.3 will be removed by the archive system once it >reaches sid. > >I can help you identifying packages that can migrate to 3.12.0. Changes already committed on experimental branch if you want to double check :) will push to bin-new when I get a full build done. Just to make sure: 1) I don't plan to maintain 3.11 at all, cherry-picking rebasing and identifying patches was a real nightmare, and this will be more and more difficult to do in the future 2) I would like to have an RC bug against 3.11 at some point in the future to make sure people migrate to 3.12 3) from 3.13 or 3.12.x I would like to make sure abi is stable and at some point stop a) hardcoding minor release into the version b) hardcoding full release into the version Depending on changes I see in the new one. I hope this can be seen as a valid forward path for json3. Also, I would like to keep the same git repo, for the new version, maybe with a 3.12 branch. This way cherry-picking it will be easier for both source packages. G.
