Got it. Thanks, guys.


On 05/20/2016 03:36 PM, Alessio Soldano wrote:
Il 20/05/2016 19:35, Weinan Li ha scritto:
- Weinan Li

On May 21, 2016, at 1:24 AM, Ron Sigal <rsigal@redhat.com> wrote:

Two questions.

1. jaxrs will continue to exist on the 3.0.x branch, right?
Right(I guess so).
Sure


        
2. More generally, what exactly goes into branch 3.0.x? I assume just bug fixes. Are they just bug fixes that come out of EAP 7? Or do all bug fixes have to be applied to both 3.0.x and master?
IMHO we should fully focus on 3.1.x from now on, and next release goes into Wildfly will be 3.1.0.
Exactly. We might decide to do another 3.0.x release if there's really 
need to (for instance should we figure out 3.0.17.Final has a critical 
issue deserving another community fix release). However the focus should 
now be on 3.1.x.

Cheers
Alessio

For 3.0.x, I guess we should treat it similar like 2.3.x, and only maintain it for EAP one-offs and CVE fixes in redhat-resteasy repo.

-Ron

On 05/20/2016 05:39 AM, Weinan Li wrote:
Hi Team,

I'm planning to remove 'jaxrs' top dir next week, which I guess will affect all the open PRs, wdyt?

--
Weinan Li / JBoss


_______________________________________________
resteasy-dev mailing list

resteasy-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/resteasy-dev
-- 
My company's smarter than your company (unless you work for Red Hat)

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


-- 
My company's smarter than your company (unless you work for Red Hat)