Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
WTP 2009-07-30
Contents
WTP Development Status Meeting
Attendees
|
|
|
Note: feel free to correct any errors/omissions in above attendance record.
Announcements And Special Reports
- ?
WTP Calendar
WTP 3.1.x
Current Build
Ready to declare latest build?
Schedule
We may want to tweak the following WTP 3.1.1 dates based on proposed ramp down dates, which will be finalized next Wed.,
- "Friday" based cycle
- 7/17 M Build
- 7/31 M Build
- 8/14 M Build
- 8/28 M Build (PMC Review starts following this build)
- 9/04 M Build (added)
- 9/11 M Build Final Build
9/18 Final Build- 9/25 Galileo SR1
- ...
- Galileo SR2 2/26/10 (will be WTP 3.1.2) (last Friday of February)
WTP 3.2
- Ready to declare latest build?
- Planning (initial plans due on or before first Milestone)
- See http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg07100.html
- For general directions, you can use the 3.1 Project Plans reference.
- Builds to be expanded: We should build our WTP 3.2 stream on both Eclipse 3.5 base, and 3.6 base, to make sure our 3.2 stream is at least compatible with both (but, we'll continue to only smoke test 3.5 based builds).
Schedule
Need to re-consider schedule to be based on "+2" dates, these are just "end dates" for the Helios Milestones, we'd be a few days earlier. Which would mess up our Friday rhythm :(
Also, need to put 3.2 and 3.1.1 on same calendar, and see what kind of trouble that causes.
- The intent is to "line up" with first four milestones of Helios Release. Our 3.2 work will also be input to any Helios builds.
M1 8/21- M1 8/14
- WTP 3.2 Plans Due
M2 10/2- M2 9/25
- Initial standard-format plans due 10/2 -- for WTP 3.3!
- M3 11/13 Start 3.2 Rampdown and PMC Review
- M4/Release 12/18
Other business
- It was asked if bugs have been open for all retrospective action items yet (answer: no) as there is still concern about builds taking so long (there are bugs to improve builds).
- There will be a new "Community Forums" front end to newsgroups. It will be even more important to make sure descriptions for our WTP groups are clear, even for the "casual user".
- To improve descriptions associated with newsgroups via Eclipse Portal:
- Use the Portal > Eclipse Projects > [view] > [maintain] Project Info Metadata > newsgroup
- Note: for those subprojects that do not have their own newsgroup (say, source editing) the metadata often now says "eclipse.webtools" with no description, but (I've heard) we can just remove those.
References
See also the WTP Meeting Archive-Reference Page.