Any plans to make new release? (0.14)

[kloczek]

I think that it wood be good make new release with current code base :)

[hawicz]

I haven't even looked to see what might be included. Are there enough changes to make a release worthwhile? Is there any particular change that you're looking to see in the next release?

[kloczek]

Since last release have been committed few changes. I think that it would be good to flush all those changes and make new release with updated code base :)

[rossburton]

Considering the last release was over a year ago, a new one would be nice.

[kloczek]

It would be as well this time change tagging patter by use in new version tag just version without date and project name to make easier to use autogenerated by github tart ball on packaging.
Please .. :)

[Croydon]

It seems like XCode 10 isn't supported by the last release, but it seems to be supported by master.

Please make a new release
and as @kloczek said please don't add the release date to the git tag, this would make packaging json-c easier

[harkue]

A new release would be welcome~

[dota17]

hi, @hawicz , maybe, it's time to prepare to release a new version. The two-year interval is a bit long. Many users expect one new version.

[hawicz]

I'd like to complete the switch over to cmake (#334) first, including eliminating all the autoconf machinery, but yes, it's well past time for a new version.
I created https://github.com/json-c/json-c/wiki/Notes-for-v0.14-release as a place to work on the release.

[kloczek]

So what is wrong with current automake/autoconf? (IMO ItWorks(tm) and nothing here needs to be changed)

[hawicz]

We've decided to switch to cmake for easier support across different environments (Linux, windows, NetBSD, Android, cross-compiling, etc...), and we don't intend to support more than one build method.

[rossburton]

I presume it's too late to suggest Meson over CMake?

[hawicz]

yes, it's too late

[besser82]

@hawicz Is there a list of items, that are currently blocking a new release? Maybe I can fix some of them…

[kloczek]

@besser82 I'm not the json-c maintainer :)

[dota17]

@besser82 you can see the Notes-for-v0.14-release.

[hawicz]

The two tasks that could use someone to take a look are:

• Analyze APIs to produce list of changes (how? eyeballs?)
• Assemble a list of issues & PRs closed (i.e. follow the steps in issues_closed_for_0.13.md that I did last time, though I just realized that that file displays terribly when actually rendered as markdown)

[besser82]

• Analyze APIs to produce list of changes (how? eyeballs?)

I've created an ABI and API diff report with the abi-compliance-checker.

@hawicz You may need your eyeballs for reading its html output. :P

[besser82]

• Analyze APIs to produce list of changes (how? eyeballs?)

I've created an ABI and API diff report with the abi-compliance-checker.

@hawicz You may need your eyeballs for reading its html output. :P

I forgot to mention that the defines for TRUE and FALSE also have been removed. That is another API break compared to earlier versions.

[hawicz]

I think I've got the tentative release notes in a pretty good shape over on the wiki page.
I'm going to give it one more read-through when I'm a bit more rested, and aim to create the json-c-0.14 branch in the next few days.

[hawicz]

json-c 0.14 has been released. See the announcement at https://groups.google.com/forum/#!topic/json-c/yLwwAqiRf-4

[kloczek]

After year IMO it would be nice to make new release again :)

Is it possible to change this time tagging patter from json-c-<version>-<date> to just <version>?
Release date is in git tag date so it is a bit redundant .. :P