Announcements and General Business
Release 3.3.1 enters +2 PMC approval stage
Do we still use this? Can we retire it? David has had some discussions with Wayne B. on this subject. Possibly time for some "fall cleaning". David discussed Wayne's suggestion to start using the top-level project for administrating the project website, as most top level projects are run this way. We can retire the website project, and initially make all PMC members and project leads members of top-level project for access to web artifacts.
3.4 Release planning
Some cleanup needed around primary platform, rampdown, and general themes Top-level plan We discussed the 3.8 platform section, as we are dedicated to support both the 4.2 and 3.8 platform's in the Juno release.
Other Business ... ?
Last week's 3.3.1 build late
Some late re-spins may have not have been necessary - all fixed now
Action items for migrating to Git
- Wiki page for education - Raghu created, Kaloyan to add content
- Setup Task force (Kaloyan)
- Mailing list entry encouraging experimentation?
Progress moving WTP 3.4 builds "officially" to 4.2 platform as the default. Carl has been working on 3.3.1 build first. Has some changes lined up to commit after 3.3.1 declares. Still planning on smoke testing on 4.2 based builds after we have resolved these issues. Our target is by M2 we will be using 4.2 based builds.
Future Agenda items
- Discuss our model and assignments of "PMC Roles". Do they still make sense?
Back to meeting list.
Please send any additions or corrections to Chuck Bridgham.