Hi, considering all the improvements in the build and testsuite recently discussed here as well as the development for JAX-RS 2.1, I believe it's time to create a 3.0.x branch and open up the master to future stuff. Any comment? Clearly this comes with the need to deal with merges of bug fixes to the 3.0.x branch... Cheers Alessio

we can run all that on widlfy public CI, but given that project doesn't properly run anywhere without disabling half of the build profile and tests, I would rather work on master and have that there. 3.0.x branch can be tested on same systems current master was. For new stuff I can setup everything on https://ci.wildfly.org/ On Fri, May 6, 2016 at 12:28 PM, Jim Ma <ema(a)redhat.com <mailto:ema@redhat.com>> wrote: +1. So we still need to find a place to run 3.0.x build ? Is there any capacity on jbossws qa machine to run resteasy 3.0.x build ? On 05/06/2016 05:49 PM, Alessio Soldano wrote: > Hi, > considering all the improvements in the build and testsuite recently > discussed here as well as the development for JAX-RS 2.1, I believe it's > time to create a 3.0.x branch and open up the master to future stuff. > Any comment? Clearly this comes with the need to deal with merges of bug > fixes to the 3.0.x branch... > Cheers > Alessio > _______________________________________________ resteasy-dev mailing list resteasy-dev(a)lists.jboss.org <mailto:resteasy-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/resteasy-dev

Hi, considering all the improvements in the build and testsuite recently discussed here as well as the development for JAX-RS 2.1, I believe it's time to create a 3.0.x branch and open up the master to future stuff.

Any comment? Clearly this comes with the need to deal with merges of bug fixes to the 3.0.x branch... Cheers Alessio -- Alessio Soldano Web Service Lead, JBoss _______________________________________________ resteasy-dev mailing list resteasy-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/resteasy-dev

Hi Tomaz, I assume you're referring to the -DskipTests that's specified by Travis CI when building the project [1] (the install command is followed by a mvn test command though). With the latest changes on current master, I'm locally building the project properly with 'mvn clean install', even on a system whose language is not English. Given some tries, what I think you need to do is running at least to the post-integration-test phase. This said, the build and test mechanism still need improvements. Cheers Alessio [1] https://s3.amazonaws.com/archive.travis-ci.org/jobs/128168659/log.txt Il 06/05/2016 12:44, Tomaž Cerar ha scritto: we can run all that on widlfy public CI, but given that project doesn't properly run anywhere without disabling half of the build profile and tests, I would rather work on master and have that there. 3.0.x branch can be tested on same systems current master was. For new stuff I can setup everything on <https://ci.wildfly.org/> https://ci.wildfly.org/ On Fri, May 6, 2016 at 12:28 PM, Jim Ma <ema(a)redhat.com&gt; wrote: > +1. > So we still need to find a place to run 3.0.x build ? Is there any > capacity on jbossws qa machine to run resteasy 3.0.x build ? > > On 05/06/2016 05:49 PM, Alessio Soldano wrote: > > Hi, > > considering all the improvements in the build and testsuite recently > > discussed here as well as the development for JAX-RS 2.1, I believe it's > > time to create a 3.0.x branch and open up the master to future stuff. > > Any comment? Clearly this comes with the need to deal with merges of bug > > fixes to the 3.0.x branch... > > Cheers > > Alessio > > > > _______________________________________________ > resteasy-dev mailing list > resteasy-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/resteasy-dev > -- Alessio Soldano Web Service Lead, JBoss

On May 9, 2016, at 4:39 PM, Rostislav Svoboda <rsvoboda(a)redhat.com&gt; wrote: > Hi, > considering all the improvements in the build and testsuite recently > discussed here as well as the development for JAX-RS 2.1, I believe it's > time to create a 3.0.x branch and open up the master to future stuff. +1, 3.0.x branch can be basically used for CP stuff I would personally prefer to have new brach per new product minor release 3.0.z for 7.0, 3.1.z for 7.1, 3.2.z for 7.2

There may be requests for some features / enhancements (not related to JAX-RS 2.1 ) in 7.1 / 7.2 / 7.3 Only bug fixes should be done in micro version of component 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.

WDYT? Rostislav > Any comment? Clearly this comes with the need to deal with merges of bug > fixes to the 3.0.x branch... > Cheers > Alessio > > -- > Alessio Soldano > Web Service Lead, JBoss > > _______________________________________________ > resteasy-dev mailing list > resteasy-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/resteasy-dev > _______________________________________________ resteasy-dev mailing list resteasy-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/resteasy-dev

On Mon, May 9, 2016 at 10:39 AM, Rostislav Svoboda <rsvoboda(a)redhat.com <mailto: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(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/resteasy-dev