Revision as of 13:39, 6 August 2009 by Thatnitind.gmail.com (Talk | contribs) (→Announcements And Special Reports)
WTP Development Status Meeting
Note: feel free to correct any errors/omissions in above attendance record.
Announcements And Special Reports
- It's New & Noteworthy time for M1.
(Weekly Google Calendar updated through December)
For Galileo and Helios overall dates, see a Simultaneous Release Calendar
No Build to declare this week ...
See also the Galileo ramp down dates
- 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)
Galileo Maintenance Plan
See WTP_3.1.x_Maintenance for documentation of scope of maintenance and approvals required.
- 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.
- The intent is to "line up" our 3.2 milestones with first four milestones of Helios Release. Our 3.2 work will also be input to any Helios builds.
- M1 8/14
- WTP 3.2 Plans Due 8/14
- M2 9/25
- Initial WTP 3.3 plans due 10/2 -- for Helios!
- M3 11/05
- After M3, start 3.2 Rampdown and PMC Review
M3 11/13 Start 3.2 Rampdown and PMC Review
- M4 and 3.2 Release Build 12/10
- We now have once-a-day Helios builds. Same WTP code. Different pre-req Platform. The goal is to make sure our 3.2 stream is at least compatible with both Galileo and Helios. Or, if we can not literally achieve being compatible, we should document why not and at least understand it.
- Any issues?
- 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.
See also the WTP Meeting Archive-Reference Page.