json-schema
json-schema copied to clipboard
voxpupuli
3.0 branch
I think we should start a branch for version 3. We'll need to keep it up to date with master, but I think that we need a place to put pull requests that either change the api or are too risky for a minor release
I have a half-baked branch I was tinkering with that drops support for multijson and yajl, I can send a PR later today. Do you think we should also release deprecation warnings on master for features that will be dropped in 3.x?
I tend to find them useful the first time I update a gem, and annoying every single test run thereafter. So I have no strong opinion.
Yes, I think we should start adding deprecation notices, although pragmatically it's best to add them at the same time as the new functionality that will replace them
I'm starting to rethink the approach to version 3. Partly because a "big-bang" release is risky, and partly because the 3.0 branch is getting stale.
Could we start releasing features (and removing features) that were for 3.0 as their own minor releases? For example, Ruby 1.8 support has been broken for a while (judging by the test results on Travis).
Or even as minor version. But either way I'd love to unblock this so we can rejuvenate the codebase
How do you mean that? Start a 3.0 which is not really ready? How about we start a 2.99.0 and start to progressively add everything one after another as patch level until we have everything we want for the first 3.0? At the same time we stop actually developing stuff for 2.6 except from bug fixes.
However, what is the difference from saying, we don't do anything more for 2.6 and start concentrating on 3.0? The actual problem is, that we haven't done anything towards 3.0 lately and this won't be solved by any changed versioning :yum: