|[wtp-dev] Minutes of the WTP Status Telecon, 2005-12-22|
Arthur - No stop-ship bugs have been proposed. We will therefore release the RC5 version as the GA version of WTP 1.0. David will copy the R build to the download directory after 12PM PST. Tim will formally announce the release of WTP 1.0 on newsgroup.
David - The Update Manager site won't be ready till first week of January.
Tim - What about that performance bug?  Can it be defered?
Arthur - Yes. It was a side effect of a late fix.
Chuck - We have investigated and confirm that it was a side effect of a fix.
Igor - I have investigated and can attach a fix. The permanent fix requires a new API.
Arthur - Igor, please create an enhancement request for the new API.
2. WTP 1.0.1 Planning - Arthur Ryman
WTP 1.0 included many important fixes, but we still have a lot of work to do in order to achieve acceptable quality. As soon as WTP 1.0 is released, we should begin fixing the bugs on the Hot List that are targetted for WTP 1.0.1. We should be creating weekly I-builds that are suitable for vendor adopter. WTP 1.0.1 should be extremely stable, i.e. no interface or UI changes unless approved by the PMC. Ideally, adopters should not even have to recompile. If interface changes are unavoidable, they should be clearly announced and supported with migration instructions. The quality of WTP 1.0.1 should steadily improve - we should have zero toleration for regressions, either functional or performance.
Lawrence - Are we only fixing Hot Bugs?
Arthur - No, but they get the highest priority.
David - Should we stagger the 1.0.1 weekly builds to allow smoke testing and avoid conflict with 1.5?
Gorkem - I prefer different days.
Arthur - Sounds like a good idea.
David - I suggest the following schedule: Monday do I-builds, Tuesday do smoke test, Wednesday declare it.
Ted - I assume all fixes will have associated bugs. Is there a way to tell which bugs are fixed in which builds?
David - I suggest we use Bugzilla. We have had a To Do on Naci's plate to generate reports from CVS (based on putting the Bugzilla id in the commit comment). EMF has tools for extracting Bugzilla info from CVS.
[action] Arthur - Investiage generating big fix reports from CVS commit comments. 
3. WTP 1.5 Planning - Tim Wagner
Tim will review the alignment of the WTP 1.5 milestone plan with the Callisto train.
Tim - The Planning Council met last week in San Francisco to discuss the Callisto release. We'll move to using their naming milestone naming after M0.
David - Our RC0 would be April 14 which is very early for a release candidate.
Tim - RC0 means bug fixing only. It's not a true release candidate. RC5 and RC6 are ship quality.
David - So RC0 is just team lead approval for bug fixes?
Tim - Yes, but we don't need to use exactly the same approval levels for each RC as the Platform.
Lawrence - What is the Platform final RC?
Tim - The intent is a freeze by RC4 unless required by downstream projects. See the published plan .
[action] Lawrence to update the Web site with the new dates 
[action] David will request new milestones to match the names used by the Platform 
David - Also let's renumber M0 to M4 so it matches the Platform milestone.
Arthur - Agreed.
Tim - Agreed.
4. Requirements Process - Jochen Krause (Tentative)
Jochen will review the requirements process if he can make this call. Otherwise, we'll defer this to the new year.
Arthur - Jochen couldn't make the call so we'll defer this.
5. Other Business -
Arthur - I created Release Notes . All components leads, please update your WTP 1.0 New and Noteworthy pages and add links to them in the Release Notes .
Lawrence - All components, please update your tutorials for WTP 1.0.
Raghu - Arthur, please add the OC4J problem to the Release Notes.
Arthur - Let's handle this using a new enhancement request bug.  Please create that and I'll add it to the WTP 1.0.1 Hot List.
Arthur - Congratulations to everyone on the release of WTP 1.0! Please take some time off to relax during the Holiday Season. We'll resume this telecon in two weeks.
IBM Software Group, Rational Division
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: firstname.lastname@example.org.
Back to the top