Project Plan For Webtools Releng, version 3.1

Introduction

The release engineering (releng) project provides builds and test frameworks for WTP.

Release Deliverables

• the Builder
• JUnit test framework
• performance test
• API tests

Table of Contents

Release Milestones

WTP Milestones follow the Eclipse release milestones by an offset of 2 as set by the Galileo release schedule.

M1	8/31/2008	M1 milestone
M2	10/01/2008	M2 milestone.
M3	11/12/2008	M3 milestone
M4	12/29/2008	M4 milestone
M5	2/06/2009	M5 milestone
M6	3/12/2009	M6 milestone.Feature complete, API and UI Freeze
M7	5/05/2009	M7 milestone. PMC review starts
RC1	5/19/2009	RC1 milestone.PMC approval required, 1 vote required
RC2	5/26/2009	RC2 milestone.PMC approval required, 2 votes required
RC3	6/02/2009	RC3 milestone.Document Freeze. PMC approval required, 3 votes required
RC4	6/09/2009	RC4 milestone.Only stop-ship defects, PMC approval required, 3 vote required
RC5	6/16/2009	RC5 milestone.Only stop-ship defects, PMC approval required, 3 vote required
GA	6/26/2009	GA

Table of Contents

Target Environments

WTP builds support only the Linux environment (though some have requested effort be put into supporting windows as well).

.

Internationalization

Internationalization and Localization will be supported.

• Internationalization (I18N)

  Each project should be able to work in an international environment, including support for operating in different locales and processing/displaying international data (dates, strings, etc.).

• Localization

  Each project should provide an environment that supports the localization of the technology (i.e. translation). This includes, but is not limited to, ensuring that strings are externalized for easy translation.

Where possible, projects should use an open and transparent process to create, maintain and deliver language packs translated into multiple languages in a timely manner. The primary languages to consider are: English, Simplified Chinese, Traditional Chinese, Japanese, French, German, Spanish.

Table of Contents

Compatibility with Previous Releases

Table of Contents

Themes and Priorities

Themes and their priorities communicate the main objectives of the project and their importance. The following themes are derived from those defined by the Eclipse Requirement council for the Eclipse Galileo release and from the WTP 3.0 release themes. These will be prioritized based on the community feedback. New themes could be synthesized from the requirements submitted by the community.

The sections to follow defines the plan items in the Server Tools project. The plan items are grouped under the respective themes where applicable. Each plan item corresponds to a new feature, API or some apsects of the project that needs to be improved. A plan item has an entry in the Eclipse Bugzilla system that has a detailed description of the plan item. Not all plan items represent the same amount of work; some may be quite large, others, quite small. Although some plan items are for work that is more pressing than others, the plan items appear in no particular order. See the corresponding bugzilla items for up-to-date status information on ongoing work and planned delivery milestones.

Other

Following are plan items that are not yet categorized into a theme.

• Committed
  • Create separate build/distributions for the Faceted Project Framework [200247] (target milestone: 3.1 M3)

• Proposed
  • Reconsider feature definitions [243264] (target milestone: 3.1)
  • Improve the way that build-tests run [243672] (target milestone: 3.1)

• Deferred
  • [releng] WTP should move the capability definitions from the runtime component to a higher one [139778] (target milestone: Future)

Table of Contents

Appendix References

1. The general WTP plan can be found here.

Table of Contents