JSR 291 Final Approval
JSR 291 just passed the Final Approval Ballot with twelve "yes" votes and two "no" votes.
Fourteen out of the sixteen Executive Committee members voted. The majority increased to ten compared to eight at the earlier ballots.
The positive comments praised the open approach of JSR 291, the suitability of the licenses, and the effectiveness of JSR 291 in influencing the other modularity JSRs. One comment urged JSR 277 and JSR 291 to become integrated, which will be achieved if JSR 277 delivers truly first class interoperation with JSR 291.
Voting comments from the detractors predictably concerned the work of the Expert Group rather than the underlying OSGi technology. They don't seem to like the JCP building on the work of other Java standards bodies. The concerns are discussed on the Expert Group mailing list and in an earlier blog.
I would like to express my thanks to many people who have contributed to the success of this JSR. They are too numerous to mention by name but include the JSR 291 Expert Group, the OSGi Alliance's Core Platform Expert Group, the Eclipse Equinox project, and numerous colleagues in IBM and elsewhere.
Fourteen out of the sixteen Executive Committee members voted. The majority increased to ten compared to eight at the earlier ballots.
The positive comments praised the open approach of JSR 291, the suitability of the licenses, and the effectiveness of JSR 291 in influencing the other modularity JSRs. One comment urged JSR 277 and JSR 291 to become integrated, which will be achieved if JSR 277 delivers truly first class interoperation with JSR 291.
Voting comments from the detractors predictably concerned the work of the Expert Group rather than the underlying OSGi technology. They don't seem to like the JCP building on the work of other Java standards bodies. The concerns are discussed on the Expert Group mailing list and in an earlier blog.
I would like to express my thanks to many people who have contributed to the success of this JSR. They are too numerous to mention by name but include the JSR 291 Expert Group, the OSGi Alliance's Core Platform Expert Group, the Eclipse Equinox project, and numerous colleagues in IBM and elsewhere.
6 comments:
Congratulations to everyone involved with JSR 291!
Having an official JSR will hopefully make it easier to sort out interoperability with other JSRs, such as 277.
Btw, I found the comment from SAS Institute Inc. very inspiring:
"This yes vote is for both the technology and the model of cooperation that has been demonstrated. The JCP Executive Committee should nurture such cooperative efforts and not downplay their importance."
Thanks Stuart. It was certainly true that the JSR 277 Expert Group started taking OSGi more seriously after JSR 291 was introduced and continues to do so.
congratulations, glyn!
Thanks Dalibor.
Congratulations, Glyn!
I followed the process since the first review last year and I must say that I strongly disagree with Sun's comment about the Rubberstamping and your work as JSR lead.
I want to thank you and the whole team for making the process so visible to everyone outside the spec team. I tend to think this inspired the JSR 277 team to come out of the dark and give us a chance to understand how a specs like seen in the first public draft has been created.
I still hope that eventually we will have two specs supplement each other. The whole discussion about what technology to prefer is current more philosophical than technical, unfortunately. Maybe the final approval of JSR 291 will help people to overcome political issues and go back focusing on the technique for the better of Java – as it was intended to be.
Thanks,
Mirko
Thanks for the feedback, Mirko.
I've enjoyed opportunities to work in the open ever since spending some time as a committer on an Apache project. It's sort of addictive...
Post a Comment