Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "WTP 2010-06-24"
(6/24) |
(→WTP 3.2.1) |
||
| Line 128: | Line 128: | ||
<!-- | <!-- | ||
* Ready to <del>declare</del> release!? Project Leads, please document your projects approval/status on our [[WTP_R3.2.0_R320_06142010| final vote page]], by Monday 6/14, at the latest. | * Ready to <del>declare</del> release!? Project Leads, please document your projects approval/status on our [[WTP_R3.2.0_R320_06142010| final vote page]], by Monday 6/14, at the latest. | ||
| − | -- | + | --> |
* No Build to declare this week (Planning week) | * No Build to declare this week (Planning week) | ||
| Line 170: | Line 170: | ||
See "references" <ref>Our plan dates are on 'Friday' of the week. But, we produce and test the build on Thursday of the week, and ideally declare on Thursday. The dates in the Google Web Tools group calendar are for 'Thursdays' since that's a calendar for committers. We give ourselves the buffer to Friday, as our "public" date, that others can pick up our build, just in case a regression is found on Thursday and we have to respin and retest. [Technically, some might say, we still have till the following Tuesday or Wednesday for some "Simultaneous Release" due dates ... but it's hard to do much in that window, without disrupting everyone ... so we'll not use that buffer, except for the worst emergencies.]</ref> for detailed explanation of what these dates mean. | See "references" <ref>Our plan dates are on 'Friday' of the week. But, we produce and test the build on Thursday of the week, and ideally declare on Thursday. The dates in the Google Web Tools group calendar are for 'Thursdays' since that's a calendar for committers. We give ourselves the buffer to Friday, as our "public" date, that others can pick up our build, just in case a regression is found on Thursday and we have to respin and retest. [Technically, some might say, we still have till the following Tuesday or Wednesday for some "Simultaneous Release" due dates ... but it's hard to do much in that window, without disrupting everyone ... so we'll not use that buffer, except for the worst emergencies.]</ref> for detailed explanation of what these dates mean. | ||
--> | --> | ||
| − | |||
== Helios Retrospective == | == Helios Retrospective == | ||
Revision as of 02:14, 24 June 2010
Contents
WTP Development Status Meeting
Attendees
|
|
|
Note: feel free to correct any errors/omissions in above attendance record.
Remember, any committer can add an agenda item. Typically, short announcements or news items go in the "Announcements" section at the beginning. Longer items or issues requiring discussion should go in the "Other business" section at end.
Announcements And Special Reports
- Congratulations on 3.2! And thank you all very much!
- Eclipse Summit Europe (ESE) 2010
- Helios in Action (2 slots!) ... How was it?
WTP Calendar
(Weekly Google Calendar updated through June, 2010)
For Helios overall dates, see a Simultaneous Release Calendar
WTP 3.2.1
- No Build to declare this week (Planning week)
- how/when to branch code? WTP_How_to:_Branching_Policy_and_Practices (updated ... but feel free to improve)
In brief, while you are doing ONLY maintenance (so maintenance and "next major release" are exactly the same code) you can develop in only HEAD, but just be sure to release to the branched map files. You can merge (or "compare") HEAD map files with branched map files, so they have the exact same version tags in both map files ... that is, there is no need to "release" twice (should have exact same version and qualifier in both builds, if code is really exactly the same).
Remember to bump service field version ... normally +1, if destined for WTP 3.2.1, +100 only required if doing service for next major release, that will not be in a service release.
Once maintenance and "next major release" code streams start to differ, we have agreed, in the past, that code in the same map file, should all be branched together, at the same time, and comments in the map file updated. This makes it easier for others to "load up" an environment for what ever stream they are working on, where as if done bundle by bundle, no one can easily figure that out what's what.
- Bug Review
Helios Retrospective
For both our specific project, and the overall Helios release.
Provide input to Planning council retrospective meeting on 7/7.
See last year's notes.
and this year's page.
Other business
- ?
References
Also, see
WTP_3.2_Ramp_down_Plan_for_Helios
See also the WTP Meeting Archive-Reference Page.