Eclipse Scout 3.9.0 Release Documentation (Draft)
Bugzilla 408757 is used to track the Scout 3.9.0 (Kepler) release review.
Review materials ready: June 5th, 2013
Review date: June 2013
This page provides the required docuware for the Scout 3.9.0 Release Review as part of the upcoming Kepler Simultaneous Release
Contact: Matthias Zimmermann(matthias.zimmermann (at) bsiag.com)
Process Documentation : 
Eclipse Scout is a mature and open framework for modern, service oriented business applications.
- Scout applications may run on diffent frontend technologies desktop (Swing, SWT), web and mobile without any changes in the source code
- Scout substantially boosts developer productivity and is simple to learn.
- User friendly applications are straight forward to implement with Scout’s comprehensive set of user interface components.
- Completely based on Java/Eclipse, Scout Applications are easy to integrate in most IT environments.
The Scout roadmap for the Kepler release has initially been discussed in the forum. From the public comments and requirements within BSI the final roamdap has been decided and presented in this blog post.
Below, the central new features for Scout 3.9.0 are listed. For a more complete overview, see the New & Noteworthy.
Scout Building (CBI)
With Kepler, the Scout build infrastructure has been moved to the CBI. For details read this blog post.
In the context of the Kepler release, all non UI Scout tests have been moved to Eclipse. In presentations and a blog post we have also talked about testing Scout applications.
- Added Support for Scout mobile and tablet applications, based on RAP 2.1
- Support for modular Scout applications
- Moved non UI tests to Eclipse
- Support to build Scout mobile applications
- Initial Support for modular Scout applications
Scout Documentation/Tutorials etc. provided on the Scout wiki
The following Scout tutorials have been added in the context of the Kepler release
- Modular Scout Applications
- JasperReport integration (contributed)
- Deploy a Scout server application to Virgo (experimental)
In addition to new and updated Scout tutorials on the wiki page, the context of the Kepler release, the Scout team has started to write a Scout book. Although the setup has been designed to encourage involvement from the community, no involvement from outside BSI has been observed so far. Current Status
- The latest Eclipse Scout Book in PDF, HTML, and EPUB.
- Setup and process description on the Scout wiki and a blog post
Status per communication channel
- Forum: OK
- Wiki: OK with additional tutorials for the new features, existing tutorials updated.
- Webpage: OK
- Mailing list: OK for important infos to all committers
We certify that the public Scout APIs in this release are production quality. As a significant amount of commercial customer applications are based on these APIs we evaluate/communicate changes accordingly
With the Scout Kepler release no significant feature is going end-of-life.
- Removal for deprecated API implemented with bug 401179
- Support for Eclipse Galileo (3.5) as we are no longer testing against this platform.
- Support for Windows XP as we are no longer testing against this platform.
- Support for RAP 1.5 (see Bug 391198 for details).
- Status: OK
- With RC4, the Kepler contribution of Eclipse Scout has no open tickets
- All release train tickets in Scout 3.9.0 List
- Overview for severety / status Scout 3.9.0 Report
Community and Support
- EclipseCon Europe: Booth, Talk + sponsored Talk
- Eclipse Finance Day Zurich: co-organisation by BSI
- Customer presentation
- OOP München: Booth
- EclipseCon Boston: Booth, Talk + sponsored Talk
- Eclipse Stammtisch Zurich: Talk + organisation by BSI
- Demo Camp München: Talk (planned)
- Demo Camp Zurich: Talk + organisation by BSI (planned)
- Customer presentation
Increasing activites on bugzilla, form and project wiki outside BSI. Kepler includes first (minor) contributions from outside BSI. All committers are currently employees from BSI.
No open IP Issues for Eclipse Scout 3.9.0. The approved IP Log is attached to 408757
The component leadership verifies that:
- The about files and use licenses are in place as per the Guidelines to Legal Documentation.
- All contributions (code, documentation, images, etc) have been committed by individuals who are either Members of the Foundation, or have signed the appropriate Committer Agreement. In either case, these are individuals who have signed, and are abiding by, the Eclipse IP Policy.
- All significant contributions have been reviewed by the Foundation's legal staff.
- All non-Committer code contributions, including third-party libraries, have been documented in the release and reviewed by the Foundation's legal staff.
- All Contribution Questionnaires have been completed.
Link to Scout Project Plan