We discussed proposing some clarifications to our API policy, and Chuck sent a draft to the mailing list
Last weeks discussion concentrated on setting expectations, and possible including clarifications on review process, but not introducing new API rules or sections to existing doc. Let's discuss further, and ensure we include most PMC members in discussion.
In last weeks Java EE planning meeting, Max Anderson (JBoss) indicated this project is essentially owned by RedHat now, and they would be interested in bringing to Eclipse. Both Konstantin and I jumped at this possibility, and have offered our help creating a proposal. Max has very limited resources at the moment, but I think we (WTP PMC) should do all we can to encourage a proposal (Help with examples etc..)
Update: Max is planning on discussing the proposal with Sonotype to get their reaction, and initially planning on incubating under m2e project. Based on their reaction, may choose to incubate under WTP. No change or proposal made yet. Will continue to engage Max to help progress.
Git adoption progress Continue polling - re-evaluate by M4 - Should we put a stake in the ground mandating when we need to see some progress in educating our committers? - investigate a subproject that could "pilot" a git repo feeding into our overall PDE build - More discussion on CVS - GIT transition - should replace CVS feature for feature - Platform HAS put a stake in the ground.... CVS Retirement bug (Target: December 21, 2012)
3.4 Release planning Top-level plan
webtool.website Progress from tracking bug
Back to meeting list.
Please send any additions or corrections to Chuck Bridgham.
Back to the top