| It’s fine to have non-critical bugs fixes in 2.1.1 as far as it doesn’t cause Jersey (and maybe other projects) TCK failures. The problem is that TCKs are not transferred to the Eclipse Foundation yet. We (Oracle) can help and temporary setup some internal TCK jobs.
— Dmitry
I also think Santiago and / or the PMC should decide about what to do with the EE4J_8 branch, as it was the PMC's invention to have it. They need to tell us the level of criticality, and the version number. Regarding the 2.1.1-SNAPSHOT, I did create that one as a collection point for all bugs (not only critical one), but I created it before the PMC invented the EE4J_8 branch. Anyways, what we do with 2.1.1-SNAPSHOT will be the actual outcome of this discussion. I do not see a need to keep it ifEE4J_8 may contain even trivial fixes. But I would propose to turn it into 2.1.2-SNAPSHOT if not. -Markus Well, maybe we need to clarify the relationship between the EE4J_8 and the 2.1.1-SNAPSHOT branches a bit more. In both cases we should only accept bugfixes to be merged into these branches. No doubt about that. The term "critical bugfix" is of course up to interpretation. Fixing broken HTML in the API docs or fixing typos could be fine for both branches. But for the EE4J_8 branch Santiago has to decide. If we keep them separate, it would be interesting to know what version we will release from the EE4J_8 branch. Will it be 2.1.1? This would conflict with the 2.1.1-SNAPSHOT branch. I know that the PMC requires us to keep the EE4J_8 branch and I'm fine with doing so. I just feels weird to have a separate 2.1.1-SNAPSHOT branch which is actually the same thing: A branch for bugfixes of JAX-RS 2.1. Depends on an organizational clarification: (A) Does the PMC allow uncritical bug fixes in their intended release basing ong EE4J_8? (B) If not, do we want want multiple bug fix release (critical ones [branch currently named "EE4J_8" with version in POM set to 2.1.1] first, then uncrititical ones [branch currently named "2.1.1" with version in POM increased from 2.1.1 to 2.1.2])? If the PMC allows uncritical bugs, we could add all existing bug fixes, so there wouldn't arise the possible need for 2.1.2. -Markus Hey Markus, what about cherry picking a few of the minor corrections to the 2.1.1 branch which are already on master? Like some of the javadoc fixes ( this and this)? Commiters, work on Jakarte EE 8 is in progress and as you know the PMC asked all subprojects to provide a release with a feature set resembling Java EE 8 plus critical fixes. For our project, this means to release JAX-RS 2.1.1 rather soon, so we need to know what is missing as of today. Santiago is already working on the TCK and I have set up a nightly build infrastructure, so everybody with a bit of free time is invited to participate: I'd like to kindly ask all committers to help with the triage, as there are 172 open issues as of now, and it is a lot of work to read and understand all of them just to learn that the issues are possibly not essential. Please check these open issues and if you are convinced that it is a critical bug, please move it to the milestone 2.2.1. And yes, please do that NOW so we have enough time to actually fix them before Jakarte EE 8 is getting published... :-) Thanks BTW, certainly everybody -including contributors- is invited to also fix bugs! :-)
--
--
|
