Jump to: navigation, search

Difference between revisions of "WTP 2009-02-12"

(Issues to watch moving up to M6 prereqs)
(Source Editing)
 
(One intermediate revision by one other user not shown)
Line 193: Line 193:
  
 
[[WTP/Build/WTP Build Rhythm Schedule|WTP Build Rhythm Schedule]]
 
[[WTP/Build/WTP Build Rhythm Schedule|WTP Build Rhythm Schedule]]
 +
 +
In addition many other good suggestions were made last week, such as release often (e.g. after every bug fix) and shorten the build/test time.
  
 
== Teams Status and Focus for Coming Week ==
 
== Teams Status and Focus for Coming Week ==
Line 198: Line 200:
 
==== Source Editing ====
 
==== Source Editing ====
 
* Ongoing triaging of incoming bug reports
 
* Ongoing triaging of incoming bug reports
* Planning M5 and working on 3.0.4
+
* Planning and working on M6
  
 
==== Server Tools====
 
==== Server Tools====

Latest revision as of 15:33, 12 February 2009

WTP Development Status Meeting

Attendees

Project Leads
Konstantin
Tim
Nitin
Kathy
Chuck
Kaloyan
Raghu
Neil
David
Philippe
Committers
Bob
Carl
Dave
Naci
Larry
Amy
Kate
Angel
Valentin
Keith
Gary
Paul
Nick
Gerry
Kiril
Friends
Chris
Eric
Elson

Note: feel free to correct any errors/omissions in above attendance record.

Announcements And Special Reports

Bob Fraser and Nova the look and feel: (see bug 261721)

WTP Calendar


Focus on Quality (Neil)

  • Focus Item:
  • Target to a specific release or "future" if planning to fix but not in the next release
  • Adjust severity as appropriate
  • Upcoming Focus item

WTP 3.0.4

Final Build. Final Testing.


3.0.4 Schedule

Jan 9 - M build
Jan 23 - M build
Jan 30 - RC1
All changes after Jan 30 require PMC approval (1 vote) (Official Ganymede RC1 date is Feb 4, we are declaring early)
Feb 6 - RC2 All changes after Feb 6 require PMC approval (2 votes) (Official Ganymede RC2 date is Feb 11, we are declaring early)
Feb 13 - final build
Feb 18 - 3.0.4 GA

Bug Lists for 3.0.4

Blockers and Critical (~5)
All 3.0.4 Hotbugs (~0)
Current 3.0.4 & 2.0.4 targeted bugs (~110, ~90,~29, ~13?)
PMC Approval Summary List


WTP 3.1

No test this week ... planning week. WTP 3.1 Project Plan Let's take a look at our plans ...

Issues to watch moving up to M6 prereqs

Schedule

Adjusted schedule, based on Platform's proposed schedule.

Normally, our milestone are one week after the Platform's delivery. Exceptions noted below.

3.0.1 Early Maintenance Release Aug 15
M1 -> Aug 22 (extra week added so not to overlap maintenance release)
3.0.2 Coordinated Maintenance Release Sep 24
M2 -> Sept 26 (extra week added so not to overlap maintenance release) (updated)
M3 -> Nov 7 (short milestone, since "making up" for added week above)
3.0.3 Early Maintenance Release Nov 14
M4 -> Dec 19
M5 -> Feb 6
3.0.4 Coordinated Maintenance Release Feb 25
(EclipseCon March 23-27)
M6 -> Mar 20 Feature Complete, API Freeze, UI Freeze, NLS, Accessibility
M7 -> May 8 Performance tuning, documentation, bug fixing
RC1 -> May 22 Serious bugs only, focus on stability.
RC2 -> May 29 WTP will likely not participate in an RC2, based on feedback from last year that RC2 came too soon, needed more fixing, less testing
RC3 -> Jun 5 Very serious bugs only.
RC4 -> Jun 12 Very very serious bugs only.
RC5 -> Jun 19 Hopefully no changes from RC4. Prepare web pages, update sites, etc.
GA -> Jun 24


Other business

What to do about weekly heartbeat?

WTP Build Rhythm Schedule

In addition many other good suggestions were made last week, such as release often (e.g. after every bug fix) and shorten the build/test time.

Teams Status and Focus for Coming Week

Source Editing

  • Ongoing triaging of incoming bug reports
  • Planning and working on M6

Server Tools

Web Services/WSDL

  1. Ongoing triage of incoming and existing bugs.
  2. Fixing and verifying bugs.

Java EE

JEE Status Meetings

Dali JPT

  • JPT 2.0
    • Working on:
      • EclipseLink support
      • Bugs for M7
      • Performance

JSF

  • Feature exceptions
  • Bug Fixes

releng

  • triage/planning

References

In general, the minimum requirement is that if you branch a plug-in, you need to branch all the plug-ins in the corresponding map file. This is to make it easier for others to know what to load, to "be current" in a maintenance branch. It is fine to branch everything in a sub-project if you choose to, but still need to correspond to what's in a map file, and the map file should be updated to explain what it's used for. Map files can be re-organized some, if that helps make it easier to organize and understand what teams are working on what.
The names for branches should follow the pattern of 'R3_0_maintenance'. This will be the name for all 3.0.x maintenance work (not just the first, 3.0.1 maintenance work). Note that JSF and JPA code may use R2_0_maintenance, but their map files, will still be branched using R3_0_maintenance.
  • Instructions for tagging existing and new WTP wiki pages can be found at WTP's Category page; remember, we can create subcategories as well
  • This Week's Smoke Test Results
WTP Smoke Test Results R30
Information about process for milestone bugzilla line item planning has been added to the WTP Bugs, Workflow, and Conventions document.
PMC Candidate Review Request Checklist - See the updated PMC Review document with attention to the "How To Prepare a PMC Defect Candidate" section
Adopter Migration Information for WTP 2.0 - Please add any details for your component.
  • Website
Documentation on Setting up your system for Web Tools Web site development and Using Web Tools Phoenix PHP templates is on the wiki at Web Tools Web Site Development.
  • Bug Day
Monitor and participate in Bug Day if you would like.
Mark any applicable bugs with keyword "bugday", but only if you'll have a representative on hand to respond through Bugzilla or in IRC
Current WTP Bug Day bugs (~53)


Project Meta data, for Project leads, especially, see "information about ..." from your subproject web page left nav bar.
Go to Foundation Portal
Login with committer ID
Click on "[maintain] Project Info meta-data"
Changes coming to IP Log management (more automated, but more for Project Leads to do?): See Development Resources/Automatic IP Log