Local (Ottawa)/International: 613-787-5018
Toll-free (NA):
1-866-842-3549
Conference ID:
9821675
Same time as well, 1 p.m. EST.
CDT 2.1.1
- Bug reports and patches have
been submitted.
- Release Date vaguely set to mid
Feb, when will start to build an RC?
CDT 3.0
- Milestones - Dates have
been purposed in the plan, but there has been little feedback to date. The
intention is that committers will indicate when there planned items will
be delivered in terms of a milestone. A milestone represents that date
make a qualified build available. See section on testing for
"qualified". (See Milestones below)
- Requirements & Designs
- are being update and posted
- Plan - Updates, version 1
Feb 10, Format eg description, status, priority bugzilla ref. ref to
design & requirements.
- APIs- As our product matures
and is increasingly used by others, the need to document and qualify the
maturity of our APIs increases. We need to determine what we
ultimately want to achieve and more importantly what we can achieve for
this release in terms of API documentation.
- Documentation of new feature
needs to be provided if you want other people to participate in the
testing of your contributions.
CDT 3.0 Testing
- Brent
-The need for a collaborated 3.0 Master Test Plan, for Component
Requirements and for Component Test Plans
Collaboration of interested parties in the testing community
will be off-line.
- Brent
- In terms of milestone quality exit criteria, I'd like to see:
M[3-6]: Build is stable and tested rigorously for a couple of
days, during which destabilizing checkins are held off. A list of
new feature functionality is announced.
To that end, I'd like to see Milestone builds produced on the
first Monday (not Friday) of the month, and the official announcement of
the tested Milestone availability presumably by Wednesday. A milestone
build which doesn't meet its quality objectives may be accepted anyhow,
deferred, extended, or branched, on a case-by-case basis as determined by
the major stakeholders.
- Publish what we are testing
- we know this will not cover everything, but at least we will know
what we are testing. This is a start.
- Publishing plans will allow
others to do testing as well.
CDT 3.X
- Is this a gleam in anyone's
eyes yet?
EclipseCon
- Open discussion here.
Recap Call on Boffs.
Other Business
CDT 3.0 Milestones in relation to Eclipse 3.1
The
milestones are:
Eclipse
3.1 M4 based builds
- Friday Jan. 7,2005 - Milestone 1 (3.0 M1) -
initial tool and process spin up
- Friday Feb. 4,2005 - Milestone 2 (3.0 M2) -
stable build reflecting progress
Eclipse
3.1 M5 Feb 18,2005
- Friday Mar. 4,2005 - Milestone 3 (3.0 M3) -
stable build reflecting progress
- Friday Apr. 1,2005 - Milestone 4 (3.0 M4) -
initial API freeze for breaking changes
Eclipse
3.1 M6 Apr 1, 2005 API complete - API freeze
- Friday May 6,2005 - Milestone 5 (3.0 M5) - API
freeze, stable build focus on clearing bug backlog
Eclispse
3.1M7 May 13, stable build - feature complete - development freeze - lock
down and testing begins
- Friday Jun. 3,2005 - Milestone 6 (3.0 M6) -
stable build, feature complete, RC0
Lock down
and external testing begins with M6 and progresses through a series of test-fix
phases against candidate releases. Release candidate builds are planned as
follows (M6 is RC0)
Note
these dates are conditional on Eclipse 3.1 schedule
- Wednesday Jun. 15,2005 - Release Candidate 1 (3.0
RC1)
- Friday Jun. 24, 2005 - Release Candidate 2 (3.0
RC2)
- Friday Jul. 1, 2005 - Release Candidate 3 (3.0
RC3)
Eclipse
3.1 GA expected ~July 1
Wednesday Jul. 13, 2005 - Release Candate 4 (3.0 RC4)
