<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, May 9, 2016 at 10:39 AM, Rostislav Svoboda <span dir="ltr"><<a href="mailto:rsvoboda@redhat.com" target="_blank">rsvoboda@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Base on this I tend to think JAX-RS 2.1 development should be done in 4.0.0-SNAPSHOT master / branch.<br>
Project structure + versions cleanup should be done before proceeding with JAX-RS 2.1 stuff to avoid clean-up of multiple branches.<br>
</blockquote></div><br><br></div><div class="gmail_extra">Yes all cleanup/restructure of the code/project should be done before JAX-RS 2.1 is worked on.<br></div><div class="gmail_extra">But given that spec is nowhere near its complete state I don't think we need to worry about that just yet.<br></div><div class="gmail_extra">Main priority is to cleanup current codebase so it can be easily mentainable for next 10 years with current functionality.<br><br></div><div class="gmail_extra">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.<br></div><div class="gmail_extra">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.<br><br></div><div class="gmail_extra">Moving master to 4 as new major version would also align better with project restructure.<br></div><div class="gmail_extra"><br>--<br></div><div class="gmail_extra">tomaz<br><br></div></div>