Hi Rebecca,

Following up on our discussion during today's meeting, changing that constructor would introduce a new behavior that may break someone's code. That was the point of the discussion in RESTEASY-975. So we have to come to some decision about how to manage changes like this. Should we have, as you suggested, a 3.0.x branch that maintains the current behavior, so that a change like this can be introduced into master (or whatever ends up serving as master for 3.1.x)?

I'm fine with this. Let's use the minor version change for this. On a related topic, we should keep track of changes like this so that we can later prepare migration notes (when we'll be ready for releasing next minor).

Cheers
Alessio

-- 
Alessio Soldano
Web Service Lead, JBoss

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