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. Raghu suggested tracking our recent decisions on api policy, and when exceptions were made. I started a wiki page here, with a query on "api" bugs. Let's discuss further, and ensure we include most PMC members in discussion.
We had a discussion several weeks ago regarding expectations for projects smoke testing each weekly declared build, and in the case of WTP 3.2.5 allowed teams to skip if they didn't contribute to the release. Last week several teams chose to skip smoke testing one or more releases (3.4 or 3.3.2).
Update: I checked in with Max, and he is still waiting on a response from Sonotype, 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