Scout/Release/LunaDoc

Eclipse Scout Release Documentation (Draft)

Bugzilla 435898 is used to track the Scout 4.0.0 (Luna) release review.

Release Review

• Review materials ready: End of May, 2014
• PMC Approval required by: June 4th, 2014
• Review date: June 11th, 2014

Content

This page provides the required docuware for the Scout 4.0.0 Release Review as part of the upcoming Luna Simultaneous Release

Contact: Matthias Zimmermann(matthias.zimmermann (at) bsiag.com)

Communication Channels:

• Scout [Forum]
• Scout [Mailing List]
• Scout [Wiki]
• Scout [Twitter]
• Scout [Blog]

Process Documentation : [1]

Overview

Eclipse Scout is a mature and open framework for modern, service oriented business applications.

• Scout applications may run on different 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.

Features

Below, the central new features for Scout 4.0.0 are listed. For a more complete overview, see the New & Noteworthy.

Scout Cloud Support

With Luna, Scout adds support to run Scout server applications on various cloud plattforms. For details. see:

• The slides of the EclipseCon Scout session
• TechTarget interview

Scout Runtime

• Added support for various updates on required software for Scout (eg. Java 8, RAP 2.3)

Scout SDK

• Added support for various updates on required software for Scout (eg. Java 8, RAP 2.3)

Non-Code Aspects

Scout Documentation/Tutorials etc. are mainly provided via the Scout Wiki

The following Scout Wiki Tutorials have been added in the context of the Luna release

• Rich Client Updater

The Scout team has updated the Scout Book book and added material regarding the use of UI widgets.

• The progress of the Scout book may be monitored in the following output directory
• Setup and process description on the Scout wiki

Status per communication channel

• Forum: OK
• Wiki: OK
• Webpage: Needs improvement
• Mailing list: OK for important infos to all committers

APIs

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

End-of-Life

With the Scout Luna release no significant feature is going end-of-life.

LIST BELOW NEEDS TO BE UPDATED

• 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).

Bugzilla

• Status: As of RC2 Scout has no unresolved critical or major bugs
• With RC4, the Luna contribution of Eclipse Scout has ? open tickets
• All release train tickets in Scout 4.0.0 List

• Overview for severety / status Scout 4.0.0 Report

Community and Support

Activities 2013

• EclipseCon Europe: Booth + Talk
• Eclipse Finance Day Zurich: Co-organisation by BSI
• Scout talk at JUG Switzerland
• Customer presentations

Activities 2014

• OOP München: Booth
• Scout talk at JUG Darmstadt
• EclipseCon San Francisco: Booth, Talk
• Javaland: Booth
• Demo Camp München: Co-organisation by BSI and Talk (planned)
• Demo Camp Zurich: Co-organisation by BSI and Talk (planned)
• Customer presentation

Current Status

• Increasing activites on the Scout forum from outside BSI.
• First large scale business applications built outside BSI are live/going live in 2014.
• All committers are currently employees from BSI.

IP Issues

Currently open IP Issues for Eclipse Scout 4.0.0:

• Missing PiggyBack CQ's for Apache Batik 1.7

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.