Our target release date is 2005-04-22.
This note summarizes the key actions that are required for us to meet that
There has been great progress in API
definition, especially in the completion of Javadoc. However, some components
have not stablised their definitions, or do not have adequate JUnit coverage.
We therefore must defer those APIs to WTP 1.1. This action will ensure
that the APIs that we do release in WTP 1.0 are built to last. The work
that has been done on the deferred APIs will put us in a great position
to complete the APIs in WTP 1.1. The extra time will also let us get extremely
valuable feedback from products that plan to use the APIs.
Therefore, all component owners should
rename their deferred APIs to "internal.provisional" asap this
week. Our goal should be to enter next week with code that is as close
as possible to the final M4 code so that we can focus on defect resolution.
2. Test Plans
All component test plans should be updated
by the end of this week, 2005-04-15. This will let us enter our test pass
3. EMF, GEF, and JEM Prerequisites
At present we are using I-builds for
EMF, GEF, and JEM. We should not release WTP milestones based on I-builds
of other components. We should cut over to milestone builds as soon as
they become available (probably Thursday for EMF and GEF, and shortly after
that for JEM) so that our test results are valid.
4. Bugzilla Bugs
All component leads should review their
defect queues and should resolve all stop-ship problems next week.
5. Third Party Content
We may obtain legal approval from the
Eclipse Foundation to redistribute some 3PC by the end of this week. If
we receive approval in time, we should incorporate the 3PC into our build
to simplify the installation process for users.
6. Ship Readiness Polls
Next week component leads should be
prepared to respond to polls with go/no-go votes based on their test results
and defect status. Any no-go vote will have to be resolved prior to us