I agree on the build refactoring being good in a major release, but to me a major release deserves actual major new features brought to the users.
So I would start by bumping up to 3.1.x , fixing the build and testsuite and than if we eventually have something related to JAX-RS 2.1 or any major new feature we move to 4.x

Cheers
Alessio

Il 09/05/2016 14:12, Tomaž Cerar ha scritto:

On Mon, May 9, 2016 at 10:39 AM, Rostislav Svoboda <rsvoboda@redhat.com> wrote:

Base on this I tend to think JAX-RS 2.1 development should be done in 4.0.0-SNAPSHOT master / branch.
Project structure + versions cleanup should be done before proceeding with JAX-RS 2.1 stuff to avoid clean-up of multiple branches.


Yes all cleanup/restructure of the code/project should be done before JAX-RS 2.1 is worked on.
But given that spec is nowhere near its complete state I don't think we need to worry about that just yet.
Main priority is to cleanup current codebase so it can be easily mentainable for next 10 years with current functionality.

What we decide to call this version doesn't really matter. I would go for something in 4.x instead of doing 3.5 or something like that.
once jax rs 2.1 work will start we can branch that to 4.x and use master for 5.x and new jax-rs spec version.

Moving master to 4 as new major version would also align better with project restructure.

--
tomaz



_______________________________________________
resteasy-dev mailing list
resteasy-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/resteasy-dev



-- 
Alessio Soldano
Web Service Lead, JBoss