Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Scout/Release/JunoDoc"

< Scout‎ | Release
(IP Issues)
(IP Issues)
 
Line 92: Line 92:
  
 
== IP Issues ==
 
== IP Issues ==
Approved IP Log is attached to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=380348 bug 380348]
+
No open IP Issues for Eclipse Scout 3.8.0. The approved IP Log is attached to [https://bugs.eclipse.org/bugs/show_bug.cgi?id=380348 bug 380348]
  
 
The component leadership verifies that:
 
The component leadership verifies that:

Latest revision as of 15:10, 31 May 2012

Eclipse Scout 3.8.0 Release Documentation (Draft)

Release Review

Review materials ready: June 6th, 2012

Review date: June 2012

Content

This page provides the required docuware for the Scout 3.8.0 Release Review as part of the upcoming Juno Simultaneous Release

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

Communication Channels:

Process Documentation : [1]

Overview

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

  • Scout applications may run on diffent frontend technologies (Swing, SWT, Web) 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 3.8.0 are listed for both the runtime and the tooling part. See the Eclipse Scout 3.8.0 New & Noteworthy for a more complete overview.

Scout Runtime

  • Support for Scout web applications, based on RAP
  • New UI Element for SVG
  • JAX-WS Support

Scout SDK

  • Support to build Scout web applications
  • Manage libraries (automatic bundle creation for selected JAR files and linking with Scout app)
  • Technology checkboxes to include support for technology X in the Scout app (X=JAX-WS, JDBC Drivers, etc.)

Non-Code Aspects

Scout Documentation/Tutorials etc. provided on the Scout wiki

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

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 (e.g. [2] or [3])

End-of-Life

We have replaced Scout Apache Axis Support by JAX-WS Support in Scout 3.8.0. The prior discussion did not turn up any objections to this.

Bugzilla


Community and Support

Activities 2011

  • Meeting Code Recommenders in Darmstadt
  • EclipseCon Europe: Booth, Talk + sponsored Talk
  • Eclipse Day Paris: Talk
  • Eclipse Stammtisch Zurich: Organized by BSI

Activities 2012

  • EclipseCon Washington: Booth, Talk + sponsored Talk
  • Eclipse Day Florence: Talk
  • Eclipse Scout Tutorial starting JavaMagazin 2012.7 (German periodical)
  • Demo Camp Bonn: Talk (planned)
  • Demo Camp Zurich: Organized by BSI
  • Demo Camp Zurich: Talk (planned)

Current Status

Observing from forum/bugzilla Scout adoption has started. First forum threas answered by adopters from outside BSI. Contributing to Scout outside of BSI has not yet been observed. All committers are currently employees from BSI.

IP Issues

No open IP Issues for Eclipse Scout 3.8.0. The approved IP Log is attached to bug 380348

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.

Project Plan

Link to Scout Project Plan [4]

Back to the top