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/Oxygen"

< Scout‎ | Release
(Dependency Upgrades)
(New Components)
Line 247: Line 247:
 
=== New Components ===
 
=== New Components ===
  
TODO
+
* jackson-core 2.8.7 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13363 CQ13363]
 +
* jackson-databind 2.8.7 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13364 CQ13364]
 +
* jackson-annotations 2.8.7 [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13365 CQ13365]
  
 
=== Dependency Upgrades ===
 
=== Dependency Upgrades ===

Revision as of 04:14, 2 June 2017

The Scout documentation has been moved to https://eclipsescout.github.io/.


Eclipse Scout DocuWare (Oxygen Release)

This page provides the required docuware for the Scout 7.0 Release Review as part of the upcoming Oxygen Simultaneous Release according to the Eclipse process documentation.

Contact: matthias(dot)zimmermann(at)bsi-software(dot)com

Communication Channels:

Release Review Dates and Links

Review Bug

This release review is tracked in TODO: update link for Scout 7.0 (link for Scout 6.0: bugzilla).

Review Dates

  • May 24/2017 - IP Log submission deadline
  • May 31/2017 - Review materials due
  • June 7/2017 - First round of release reviews (aim for this date if you can)
  • June 21/2017 - Second (final?) round of release reviews
  • June 28/2017 - Eclipse Oxygen GA

Original source is here

Additional Links

Overview

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

  • Scout HTML5 client applications may run on the desktop, on tablets and on mobile phones 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, Scout Applications are easy to integrate in most IT environments.

Features

TODO

Roadmap for 2017/18

TODO

Milestone Installations

Please follow the steps below.

  1. Prior to the Eclipse Neon Release download the Scout EPP from the Developer Builds
  2. Download and Install the Scout SDK
  3. The Scout "Hello World!"

Non-Code Aspects

Scout Documentation/Tutorials etc. is written with Asciidoctor and hosted on Github. The progress of the Scout book may be monitored in the following output directory

Status per communication channel

  • Forum: OK
  • Wiki: OK
  • Webpage: OK
  • Mailing list: OK for important info 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.

Compatibility with Previous Releases

Scout RT 7.0 will NOT be compatible with Scout 7.0.

Scout SDK 7.0 will NOT be compatible with Scout SDK 5.0.

We try to make migration to new releases as easy as possible, however to keep our code clean and simple we need to change the API in new releases. There are no more API changes after milestone M6.

API Compatibility rules are described in the contribution guidelines in more detail.

For changes from Scout 6.0 to 7.0 Migration see the Eclipse Scout Migration Guide

End-of-Life

With Scout release 7.0 no significant components reach their end-of-life. Therefore, no substantial migration efforts are anticipated for migrating a Scout application from release 6.0 to release 7.0.

Ramp down Policy

We use daily builds. No API changes after M6, no new features after M7. In the RC phase only bugs marked P2 or higher or severity major or higher will be fixed.

Bugzilla Tickets

Bug reports relevant to the Scout 6.0 release

Target Environment

JRE

All of Eclipse Scout is "pure" Java code and has no direct dependence on the underlying operating system. The chief dependence is therefore on the Java Runtime (JRE) itself. The Scout 6.0 runtime is still compatible with Java SE 7. As the announced end of public updates for Java 7 is scheduled for April 2015, Scout projects working with Oracle products might want to consider moving to Java 8 as soon as possible.

The eclipse scout package only runs with Java >=8.

Java Version Support for Scout Runtime/SDK
8 recommended
9 experimental

Eclipse Platform

For Scout 6.0 we recommend developing Scout with Eclipse Neon (4.6).

The following Eclipse platforms are supported:

Eclipse Version Scout Runtime Scout SDK
Luna (4.4) - supported
Mars (4.5) - supported
Neon (4.6) - recommended

Browser Versions

The HTML5 UI for Scout only supports the following browsers and versions:

TO BE VERIFIED

  • Microsoft Internet Explorer >= version 9
  • Google Chrome >= version 36
  • Firefox >= version 36
  • Safari >= TBD
  • iOS >= TBD
  • Android >= TBD

Tested Platforms

We focus our testing on a handful of popular combinations (OS, HW Arch, Java VM, Eclipse platform); these are our reference platforms.

Scout undoubtedly runs fine in many operating environments beyond the reference platforms we test. However, since we do not systematically test them we cannot vouch for them. Problems encountered when running Scout on a non-reference platform that cannot be recreated on any reference platform will be given lower priority than problems with running Scout on a reference platform.

Scout 6.0 will be tested and validated on the following reference platforms:

Operating System OS Version Hardware Java VM (vendor, version, arch) Eclipse Platform (version, arch)
Windows 7 x86 64-bit
Oracle JDK 7, 64-bit 4.6, 64-bit, EPP
Oracle JDK 8, 64-bit 4.6, 64-bit, EPP
10 Oracle JDK 8, 64-bit 4.6, 64-bit, EPP
Ubuntu Linux 15.10 OpenJDK 7, 64-bit 4.6, 64-bit, EPP
Apple Mac OS 10.8 Oracle JDK 7, 64-bit 4.6, 64-bit, EPP

With Scout 6.0 we no longer explicitly test our bits on 32bit architectures.

Build Process

Scout is built on Hudson @ Eclipse.

Scout is using maven and tycho for building.

  • Gerrit Jobs run build against lowest target platform with runtime unit tests
  • Nightly Jobs run against all platforms with all unit tests
  • Release Jobs can be parameterized for a specific tag and deploy to a specific updatesite
  • Some tests currently still run only at BSI's infrastructure: Scout GUI tests using java.awt.Robot, because they need a fully-fledged desktop environment.

Scout Maven Artifacts uploaded to repo.eclipse.org

Current Project Metrics

project metrics for Eclipse Scout provided on [openHub]

Community and Support

Activities 2016

  • 3rd Eclipse Scout User Group Meeting (Eclipsecon Europe Unconference)
  • EclipseCon Europe
  • Devoxx Antwerpen
  • Democamp December Munich December
  • Gemeinsam BSI (Conference organized by BSI for its customers)

Activities 2017

  • Javaland (planned)
  • Democamp Munich (planned)
  • Democamp Zurich (planned)
  • Java Forum Stuttgart (planned)

Current Status

  • Successful transition of many projects on new Java/HTML5 stack
  • Increasing activites on the Scout forum and on Stackoverflow
  • Large scale Eclipse Scout business applications built and in productive use
  • All committers are currently employees from BSI

IP Status

New Components

Dependency Upgrades

IP Log

The state of the IP log is tracked with this bug. Scout's IP Log for Scout has been generated according to the Wiki description.

To check the current state at any time, use the following link. To compare against potential issues use this IP Issues List. Caution: The link reporting potential issues contains many bogus links. See below for a partial list

Known bogus issues in IP issues list:

  • ant-*
  • derby*
  • junit.jar
  • servletbridge.jar


TODO: The Scout IP Log has been approved on [pending]. 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.

Previous Release Documentation

Back to the top