In order to remain current, each Eclipse Project release targets reasonably current operating environments.

In order to remain current, each Eclipse Project release targets reasonably current operating environments.

−

−

The following information needs to be verified/updated:

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.

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.

−

In general, the 3.9 release of Eclipse Scout is developed on an Oracle Java SE 7 VM. As such, Scout is targeted at all modern, desktop Java VMs. Most functionality is available for Java SE 7 level development everywhere, and extended development capabilities are made available on the VMs that support them.

+

In general, the 3.9 release of Eclipse Scout is developed on an Oracle Java SE 6 VM. As such, Scout is targeted at all modern, desktop Java VMs. Most functionality is available for Java SE 6 level development everywhere, and extended development capabilities are made available on the VMs that support them.

There are many different implementations of the Java Platform running atop a variety of operating systems and various CPU architectures. Beside that Scout 3.9 also runs on various Eclipse platforms. For Kepler release of Scout the following Eclipse platforms are supported:

There are many different implementations of the Java Platform running atop a variety of operating systems and various CPU architectures. Beside that Scout 3.9 also runs on various Eclipse platforms. For Kepler release of Scout the following Eclipse platforms are supported:

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.

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 3.9 will be tested and validated on the following reference platforms (this list is updated over the course of the release cycle):

+

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

{|border="1" cellpadding="5" cellspacing="0"

{|border="1" cellpadding="5" cellspacing="0"

Line 64:

Line 64:

|x86 32-bit

|x86 32-bit

|rowspan="5"|Oracle, 1.6, 32-bit

|rowspan="5"|Oracle, 1.6, 32-bit

−

|3.8.0, 32-bit

+

|4.3, 32-bit

|-

|-

|rowspan="6"|x86 64-bit

|rowspan="6"|x86 64-bit

−

|3.5.2, 32-bit

−

|-

|3.6.2, 32-bit

|3.6.2, 32-bit

|-

|-

|3.7.2, 32-bit

|3.7.2, 32-bit

|-

|-

−

|3.8.0, 32-bit

+

|3.8.2, 32-bit

+

|-

+

|4.2.2, 32-bit

|-

|-

|Oracle, 1.6, 64-bit

|Oracle, 1.6, 64-bit

−

|4.2.0, 64-bit

+

|4.3, 64-bit

|-

|-

|Oracle, 1.7, 64-bit

|Oracle, 1.7, 64-bit

−

|4.2.0, 64-bit, EPP

+

|4.3, 64-bit, EPP

|-

|-

−

|rowspan="2"|XP

+

|rowspan="2"|8

−

|rowspan="2"|x86 32-bit

+

|rowspan="2"|x86 64-bit

−

|Oracle, 1.7, 32-bit

+

|Oracle, 1.7, 64-bit

−

|4.2.0, 32-bit, EPP

+

|4.3, 64-bit, EPP

|-

|-

|Oracle, 1.6, 32-bit

|Oracle, 1.6, 32-bit

−

|3.8.0, 32-bit

+

|4.3, 32-bit

|-

|-

−

|rowspan="5"|Ubuntu Linux

+

|rowspan="3"|Ubuntu Linux

−

|rowspan="5"|12.04 LTS

+

|rowspan="3"|12.10

|x86 64-bit

|x86 64-bit

|OpenJDK, 1.7, 64-bit

|OpenJDK, 1.7, 64-bit

−

|4.2.0, 64-bit, EPP

+

|4.3, 64-bit, EPP

−

|-

+

−

|rowspan="4"|x86 32-bit

+

−

|Oracle, 1.6, 32-bit

+

−

|rowspan="2"|3.8.0, 32-bit

+

−

|-

+

−

|Oracle, 1.7, 32-bit

+

|-

|-

+

|rowspan="2"|x86 32-bit

|OpenJDK, 1.7, 32-bit

|OpenJDK, 1.7, 32-bit

−

|rowspan="2"|4.2.0, 32-bit, EPP

+

|rowspan="2"|4.3, 32-bit EPP

|-

|-

|Oracle, 1.6, 32-bit

|Oracle, 1.6, 32-bit

|-

|-

|rowspan="3"|Apple Mac OS

|rowspan="3"|Apple Mac OS

−

|rowspan="3"|10.7 (Lion)

+

|rowspan="3"|10.8

|rowspan="3"|x86 64-bit

|rowspan="3"|x86 64-bit

|Oracle, 1.7, 64-bit

|Oracle, 1.7, 64-bit

−

|3.8.0, 64-bit

+

|4.3, 64-bit

|-

|-

|rowspan="2"|Apple, 1.6, 64-bit

|rowspan="2"|Apple, 1.6, 64-bit

−

|4.2.0, 32-bit, EPP

+

|4.3, 32-bit, EPP

|-

|-

−

|4.2.0, 64-bit, EPP

+

|4.3, 64-bit, EPP

|}

|}

Line 125:

Line 120:

*Apple Safari 5

*Apple Safari 5

−

== Compatibility with Previous Releases ==

−

'''Scout RT 3.8''' will be upwards compatible with Scout RT 3.7 except in those areas noted in the release notes. Programs that use affected APIs and extension points will need to apply the migrations described in [[Scout/Migration/3.8]].

+

=== Mac OSX and JDK1.7 ===

−

All migrations are also described in in the [[http://wiki.eclipse.org/Scout/Migration/3.8#Release_Notes release notes]]:

+

With MacOSX there is a Problems with SWT/AWT Bridge in JDK1.7. See following Bugs: [http://bugs.sun.com/view_bug.do?bug_id=7154778 NSView-based implementation of sun.awt.EmbeddedFrame], [https://bugs.eclipse.org/bugs/show_bug.cgi?id=374199 SWT_AWT bridge broken by openjdk 1.7.0_04ea].

−

'''Scout SDK 3.8''' will NOT be upwards compatible with Scout SDK 3.7. Currently, the Scout SDK API is not yet used frequently.

+

== Compatibility with Previous Releases ==

−

== Support for Eclipse 3.8 workbench ==

+

'''Scout RT 3.9''' will be downwards compatible with your Scout 3.8 workspace except in those areas noted in the release notes. Programs that use affected APIs and extension points will need to apply the migrations described in [[Scout/Migration/3.9]].

−

While Juno plans to provide Eclipse 4.2 as the primary platform, the Eclipse Project will also be providing a 3.8 based version as well. This is done since it is anticipated some adopters may not be able to move to 4.2 right away, and may need to wait for their own "release train" to get lined up.

+

'''Scout SDK 3.9''' will NOT be upwards compatible with Scout SDK 3.8. Currently, the Scout SDK API is not yet used frequently.

−

We will support our adopters in a similar way: Eclipse Scout will support 3.8 as a secondary platform (while 4.2 will be the primary platform). But we anticipate having only one stream of development. Scout will continue to work with the 3.8 and 4.2 platform, using the compatibility layer, and no 4.2 specific APIs. For Juno we will make sure that Scout will also compile against 3.8 (and 3.7, 3.6, 3.5) to ensure that we do not introduce new API useage that breaks compatibility.

+

== Support for Eclipse 3.x workbench ==

−

However, we will focus our testing efforts on 4.2. We will accept bugs as equally valid if they are reported when running on another Eclipse platform. We will provide this type of one-stream, multi-platform support for Juno and its two coordinated maintenance releases.

+

As Scout supports Eclipse 3.6 - 4.3 we will continue to support the 3.x workbench. This is done since it is anticipated some adopters may not be able to move to 4.3 right away, and may need to wait for their own "release train" to get lined up.

−

== Build Process ==

+

But we anticipate having only one stream of development. Scout will continue to work with the 3.x and 4.x platform (using the compatibility layer) and no 4.x specific APIs. For Kepler we will make sure that Scout will compile against 4.3 (and 4.2, 3.8, 3.7, 3.6) to ensure that we do not introduce new API useage that breaks compatibility.

−

Scout is built using [http://ant.apache.org/ ant] and [[PDE/Build | pde]] feature build. Builds are executed nightly (artifacts see [http://www.eclipse.org/scout/downloads/ Scout downloads]) and per milestone and release.

+

−

'''Sources:'''

+

However, we will focus our testing efforts on 4.3. We will accept bugs as equally valid if they are reported when running on another Eclipse platform. We will provide this type of one-stream, multi-platform support for Kepler and its two coordinated maintenance releases.

−

* The scripts are available here: [https://dev.eclipse.org/svnroot/technology/org.eclipse.scout/scout.builder/branches/3.8/org.eclipse.scout.releng SVN].

+

−

* Custom ant tasks for used in the build (e.g. for packing plugins and waiting until the jars are signed) are available here: [https://dev.eclipse.org/svnroot/technology/org.eclipse.scout/scout.builder/branches/3.8/org.eclipse.scout.releng.ant SVN]

+

−

'''Hudson:'''

+

== Build Process ==

−

Both nightly and milestone builds are done with the job [https://hudson.eclipse.org/hudson/job/cbi-scout-3.7/ cbi-scout-3.7] for all versions using different parameters.

+

−

+

−

=== Checklist for building Scout milestones ===

+

−

+

−

==== +0 Day====

+

−

# Check version: versionMajor,versionMinor,versionMicro

+

−

# Check orbit drop: (latest stable)

+

−

# Make sure, that features dependent on rap runtime are disabled (because rap rt is usually not aggregated at +0): org.eclipse.scout.rt.rap.feature.feature.group

Bugzilla Tickets

Target Environment

In order to remain current, each Eclipse Project release targets reasonably current operating environments.

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.

In general, the 3.9 release of Eclipse Scout is developed on an Oracle Java SE 6 VM. As such, Scout is targeted at all modern, desktop Java VMs. Most functionality is available for Java SE 6 level development everywhere, and extended development capabilities are made available on the VMs that support them.

There are many different implementations of the Java Platform running atop a variety of operating systems and various CPU architectures. Beside that Scout 3.9 also runs on various Eclipse platforms. For Kepler release of Scout the following Eclipse platforms are supported:

Eclipse Helios (3.6)

Eclipse Indigo (3.7)

Eclipse Juno (3.8 / 4.2)

Eclipse Kepler (4.3)

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 3.9 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 32-bit

Oracle, 1.6, 32-bit

4.3, 32-bit

x86 64-bit

3.6.2, 32-bit

3.7.2, 32-bit

3.8.2, 32-bit

4.2.2, 32-bit

Oracle, 1.6, 64-bit

4.3, 64-bit

Oracle, 1.7, 64-bit

4.3, 64-bit, EPP

8

x86 64-bit

Oracle, 1.7, 64-bit

4.3, 64-bit, EPP

Oracle, 1.6, 32-bit

4.3, 32-bit

Ubuntu Linux

12.10

x86 64-bit

OpenJDK, 1.7, 64-bit

4.3, 64-bit, EPP

x86 32-bit

OpenJDK, 1.7, 32-bit

4.3, 32-bit EPP

Oracle, 1.6, 32-bit

Apple Mac OS

10.8

x86 64-bit

Oracle, 1.7, 64-bit

4.3, 64-bit

Apple, 1.6, 64-bit

4.3, 32-bit, EPP

4.3, 64-bit, EPP

The RAP (Rich Ajax Platform) UI for Eclipse Scout requires at least the following browser versions:

Mac OSX and JDK1.7

Compatibility with Previous Releases

Scout RT 3.9 will be downwards compatible with your Scout 3.8 workspace except in those areas noted in the release notes. Programs that use affected APIs and extension points will need to apply the migrations described in Scout/Migration/3.9.

Scout SDK 3.9 will NOT be upwards compatible with Scout SDK 3.8. Currently, the Scout SDK API is not yet used frequently.

Support for Eclipse 3.x workbench

As Scout supports Eclipse 3.6 - 4.3 we will continue to support the 3.x workbench. This is done since it is anticipated some adopters may not be able to move to 4.3 right away, and may need to wait for their own "release train" to get lined up.

But we anticipate having only one stream of development. Scout will continue to work with the 3.x and 4.x platform (using the compatibility layer) and no 4.x specific APIs. For Kepler we will make sure that Scout will compile against 4.3 (and 4.2, 3.8, 3.7, 3.6) to ensure that we do not introduce new API useage that breaks compatibility.

However, we will focus our testing efforts on 4.3. We will accept bugs as equally valid if they are reported when running on another Eclipse platform. We will provide this type of one-stream, multi-platform support for Kepler and its two coordinated maintenance releases.

Build Process

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.

Unit Tests

Unit tests are executed during the nightly build of Eclipse Scout RT and Eclipse Scout SDK. The test suites contain simple unit tests as well as GUI tests. The latter are based on Scout's testing support bundles which is built on top of java.awt.Robot. Therefore our GUI tests require a fully-fledged desktop environment. The tests are currently executed on BSI's infrastructure.