|RE: [wtp-dev] Minutes of the WTP Status Telecon, 2006-04-27|
> A WTP 1.5 should also be able to work on projects created by WTP 2.0 users
> and shared via a repository. Any new artifacts creates by WTP 2.0 should not
> break WTP 1.5. WTP 1.5 should either ignore or tolerate any new artifacts
> created by WTP 2.0.
I don’t think this is a good idea. By the time we are working on 2.0, 1.5 will be done. What it can and cannot ignore or tolerate will be fixed. Having this requirement will seriously hamper our ability to deliver new functionality not yet envisioned in the 2.0 release. I do agree that a project created on 1.5 should not be auto-upgraded when it’s opened in 2.0 unless the user explicitly agrees to the upgrade, however I don’t think we should require projects created in 2.0 (or those that have been upgraded) to continue working on 1.5.
Behalf Of Arthur Ryman
The following action items are currently open . Action items owners should update their status in Bugzilla prior to the status telecon. Thx.
Jeff - Updates in bugzilla.
2. WTP 1.0.2 Status
- David Williams
David - Was scheduled to announce yesterday, but found a bug. So we held off the announcement. Want to discuss it before declaring.
David - At the PMC call tuesday, we agreed to have a 1.0.3 maintenance stream. My recommandation is to fix this bug in 1.0.3. Do a build before andy other fixes gets in so that the community can use that build.
Tim - What's the impact of this bug?
David - It affects update manager. Also, if users want to debug WTP, the they need to get the code from CVS directly. Platfrom see this as a permanent limitation, so we just have to live with it.
David - If no objections, I'll declare 1.0.2 in the afternoon? Congratulation everyone on this achievement.
David - Please hold off releasing anything to the maintenance stream (1.0.3) until this bug is fixed and the update manager site is ready.
David - Also, I suggest all 1.0.3 fixes require some level of PMC approval.
Arthur - Agree.
Tim - Each build should be treated as a release candidate, so no regression.
Ted - What's the process for approval? Send request to the wtp-dev list?
David - Yup, send request to wtp-dev list and PMC members will vote in the bugzilla.
Jeff - Any dates for 1.0.3?
David - TBD.
Arthur - I think we need to see how adopters are coming along with 1.0.2. If adopters ship 1.0.2 to customers, it will generate bugs. We need to see what's the incoming rate and then determine the dates.
3. WTP 1.5 Status
3.1 WTP 1.5 Build Status - David Williams
David - RC2 is building fine. RC2 will be next Friday according to the Callisto schedule. Our prereqs will probably release sometime Wed. We'll spend Thurs smoke test and declare on Fri.
David - There are some failing JUnit testcases that Chuck and I were talking about. Chuck cannot reproduce them under Windows. Jeff, can we get test results for these test under another Linux machine?
David - After RC2, fixes will need component lead approval. Also, I believe it's after RC4 that all projects will announce the bugs that will be fixed.
Ted - We need to get an architecture review of the thread safety issue?
Chuck - I'm out next week, we can do it the following Monday.
David - For next week, component lead should have triage all the bugs so that we can get an accurate count of the number of P1, P2 and etc.
3.2 WTP 1.5 Hot Bugs 
- Jeffrey Liu
Ted - Are we using the new hot bug process.
Jeff - Yes, my fault, forgot to include the queries in the minutes.
4. Other Business - Open
Arthur - I ran into problems when opening old projects with 1.5. The projects don't show up.
Chuck - If you open it with the old navigator, you won't see anything.
Arthur - Not just for Web projects, same goes for any projects.
David - Sounds like a platform bug.
Chuck - I've tried it before and it worked.
Arthur - What's the story for 1.0.2 and 1.5 co-existence?
Chuck - We support it.
Jeff - What about scenario like this one: create project with 1.0.2, check into CVS. Check out project using 1.5, modify something (ex. generate a Web service). Check project into CVS. Open project again with 1.0.2, will this work?
David - Sounds like a good testcase to try.
Arthur - We need to spell out the scenarios that we support when we do the requirements for 2.0.
David - Goal is to be consistent with the Platform.
David - Another testcase: set preference in 1.0.2. Open the same workspace with 1.5 and make sure all the preferences are still valid. Preference sometimes change names, in which case, migration is needed.
Kathy - Are we not going to declare an I build this week? Meaning we do not need to hold back on releasing?
David - Plan is to not declare one. But keep in mind that we are in shut down mode, so every build should have some level of stability.
Kathy - We have quite a few fixes this week, would be nice to have an I build declared.
David - Anyone else want one this week?
Chuck - I would vote for one.
David - OK.
Tim - We have some problems generating the usage report using the API scanner.
Jeff - I'll take a look and reply to your note.
_______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.