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 "2006-11-30"
Line 8: | Line 8: | ||
:*Conferences: | :*Conferences: | ||
− | ::[http://www.eclipsecon.org/2007/ EclipseCon2007] open for long talks, short talks | + | ::[http://www.eclipsecon.org/2007/ EclipseCon2007] open for long talks (Dec 1), short talks (Jan 15) submissions. |
::[http://2007.ecoop.org ECOOP] is open for submissions -- Berlin, Germany, July 30 - August 3, 2007. | ::[http://2007.ecoop.org ECOOP] is open for submissions -- Berlin, Germany, July 30 - August 3, 2007. | ||
:*Reminder: Make sure your repository connections are using "cvsroot" and not "home" | :*Reminder: Make sure your repository connections are using "cvsroot" and not "home" | ||
− | :*Announcement: Update on committer status for Valentin Baciu - Tim W? | + | :*Announcement: Update on committer status for Valentin Baciu - Tim W? Tweaks to voting system? |
Line 34: | Line 34: | ||
;WTP 2.0 | ;WTP 2.0 | ||
− | :* | + | :*Integration Build this Friday, 12/01/06 |
::Build Status? David | ::Build Status? David | ||
+ | :::WTP 2.0 now requires a Java5 runtime. However, components should not start adding hard Java5 dependencies. | ||
+ | :::What's the third party jar status? | ||
:::Please smoke test the latest Integration I-build to be declared by noon on Friday. | :::Please smoke test the latest Integration I-build to be declared by noon on Friday. | ||
− | + | ::Should the 2.0 builds have a combined zip which includes JPA and JSF, possibly ATF, like it does for WST, JST? | |
:*Need to improve the [[Web_Tools_Platform_2.0_Plan|WTP 2.0 Plan]] document | :*Need to improve the [[Web_Tools_Platform_2.0_Plan|WTP 2.0 Plan]] document | ||
::Begin to analyze [http://www.eclipse.org/webtools/development/apiscanner/reports/main.html Adopter Usage Reports] to pick most important API requirements. | ::Begin to analyze [http://www.eclipse.org/webtools/development/apiscanner/reports/main.html Adopter Usage Reports] to pick most important API requirements. | ||
− | :::Component leads should analyze for two reasons | + | :::Component leads should analyze for two reasons: |
::::*To ensure no one is using code they should not be using. | ::::*To ensure no one is using code they should not be using. | ||
::::*To prioritize which code you plan to make API. | ::::*To prioritize which code you plan to make API. | ||
Line 52: | Line 54: | ||
::[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Web+Tools&target_milestone=---&target_milestone=2.0&target_milestone=2.0+M1&target_milestone=2.0+M2&target_milestone=2.0+M3&target_milestone=2.0+M4&target_milestone=2.0+M5&target_milestone=2.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=%7C%2C, Blockers, Criticals] (~7) | ::[https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=WebTools&product=Web+Tools&target_milestone=---&target_milestone=2.0&target_milestone=2.0+M1&target_milestone=2.0+M2&target_milestone=2.0+M3&target_milestone=2.0+M4&target_milestone=2.0+M5&target_milestone=2.0+M6&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=%7C%2C, Blockers, Criticals] (~7) | ||
+ | :*Migration testing | ||
+ | :*Proposal: Milestone To Do - Clean up all resolved defect verifications for the given milestone. | ||
;Other business? | ;Other business? | ||
+ | :*Java EE 5 Update - Chuck? | ||
+ | :*EclipseCon Update - Tim W? | ||
:*Website Update - Tim W? | :*Website Update - Tim W? | ||
:*Just a friendly reminder to fill in your team status each week on the meeting agenda. | :*Just a friendly reminder to fill in your team status each week on the meeting agenda. |
Revision as of 12:52, 29 November 2006
WTP Development Status Meeting 2006-11-30
- Attendees
- Announcements and Reminders
- Conferences:
- EclipseCon2007 open for long talks (Dec 1), short talks (Jan 15) submissions.
- ECOOP is open for submissions -- Berlin, Germany, July 30 - August 3, 2007.
- Reminder: Make sure your repository connections are using "cvsroot" and not "home"
- Announcement: Update on committer status for Valentin Baciu - Tim W? Tweaks to voting system?
- WTP 1.5.3
- Due: 2007-02-16
- 1.5.3 Guidelines for fixes
- We will be declaring a 1.5.3M build this week so please smoke test the latest M-build to be declared by noon on Friday.
- Build status? David
- Bug lists
- Resolved, Unverified (~220)
- Older resolved defects closed out. Minor glitch in closing out those in the remind and later states has been corrected.
- Verified, Not closed (~0)
- 1.5.3 Hot Bug Requests (~2)
- New process, when you reject a hot bug request as a hot bug, change the summary to [hotbug_declined].
- 1.5.3 Hot Bugs (~1)
- Blockers, Criticals (~2)
- WTP 2.0
- Integration Build this Friday, 12/01/06
- Build Status? David
- WTP 2.0 now requires a Java5 runtime. However, components should not start adding hard Java5 dependencies.
- What's the third party jar status?
- Please smoke test the latest Integration I-build to be declared by noon on Friday.
- Should the 2.0 builds have a combined zip which includes JPA and JSF, possibly ATF, like it does for WST, JST?
- Need to improve the WTP 2.0 Plan document
- Begin to analyze Adopter Usage Reports to pick most important API requirements.
- Component leads should analyze for two reasons:
- To ensure no one is using code they should not be using.
- To prioritize which code you plan to make API.
- Component leads should analyze for two reasons:
- Bug lists
- Untriaged (~115)
- Resolved, Unverified (~70)
- Verified, Not closed (~0)
- 2.0 Hot Bug Requests (~1)
- 2.0 Hot Bugs (~0)
- Blockers, Criticals (~7)
- Migration testing
- Proposal: Milestone To Do - Clean up all resolved defect verifications for the given milestone.
- Other business?
- Java EE 5 Update - Chuck?
- EclipseCon Update - Tim W?
- Website Update - Tim W?
- Just a friendly reminder to fill in your team status each week on the meeting agenda.
Teams Status and Focus for Coming Week
- Common Component Team
- Server Component Team
- Datatools (RDB, 1.5.x only)
- XML-JSP Component Team
- Web Services Component Team
- Java EE Component Team
- Dali/JPA
- JSF
- DTP
- ATF
- Website
- releng
- Execution Environments
- Add versions 1.5.1,1.5.2,1.5.3 to the WTP bugzilla version options list when opening new bugs