Difference between revisions of "Scout/Release/Kepler"

From Eclipsepedia

Jump to: navigation, search
(Eclipse Scout (Kepler Release))
(Eclipse Scout (Kepler Release))
 
(27 intermediate revisions by 5 users not shown)
Line 1: Line 1:
 +
{{ScoutPage|cat=Release 3.9}}
 
= Eclipse Scout (Kepler Release) =
 
= Eclipse Scout (Kepler Release) =
 
[[Image:ScoutIcon32c.jpg]]
 
[[Image:ScoutIcon32c.jpg]]
Line 5: Line 6:
  
 
* Eclipse Scout is a mature and open framework for modern, service oriented business applications.
 
* Eclipse Scout is a mature and open framework for modern, service oriented business applications.
 +
* Scout comes with multi-frontend support for desktop (Swing and SWT), web, and mobile/tablet clients.
 
* Scout substantially boosts developer productivity and is simple to learn.
 
* 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.
 
* User friendly applications are straight forward to implement with Scout’s comprehensive set of user interface components.
Line 10: Line 12:
  
 
Useful Links
 
Useful Links
* Plan: [http://www.eclipse.org/projects/project-plan.php?planurl=eclipse/development/plans/eclipse_project_plan_4_3.xml Kepler project plan]
+
* Overview: [http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan Kepler release overview]
 +
* Platform Plan: [http://www.eclipse.org/projects/project-plan.php?planurl=eclipse/development/plans/eclipse_project_plan_4_3.xml platform project plan]
 
* Schedule: [https://www.google.com/calendar/embed?src=gchs7nm4nvpm837469ddj9tjlk@group.calendar.google.com&ctz=America/New_York&gsessionid=OK Kepler release train schedule]
 
* Schedule: [https://www.google.com/calendar/embed?src=gchs7nm4nvpm837469ddj9tjlk@group.calendar.google.com&ctz=America/New_York&gsessionid=OK Kepler release train schedule]
* Reports: [http://build.eclipse.org/juno/simrel/ Simrel reports]
+
* Reports: [http://build.eclipse.org/simrel/kepler/reporeports/ Simrel reports]
  
 
== Scout Release Review Documentation ==
 
== Scout Release Review Documentation ==
* '''{{ScoutLink|Release|KeplerDoc|Documentation|name=Scout Kepler Documentation}}''' - in progress
+
* '''{{ScoutLink|Release|KeplerDoc|Documentation|name=Scout Kepler Documentation}}''' - Docuware for the Scout 3.9.0 release review
 
+
== Planning Document ==
+
Link to project plan as [[http://www.eclipse.org/scout/plan/plan.3.8.xml XML document]]
+
  
 
== New and Noteworthy ==
 
== New and Noteworthy ==
  
{{ScoutLink|NewAndNoteworthy|name=New and Noteworthy}}
+
{{ScoutLink|NewAndNoteworthy|3.9|name=New and Noteworthy}}
  
 
== End-of-Life ==
 
== End-of-Life ==
 +
With the Scout Kepler release no significant feature is going end-of-life.
  
With Scout 3.9 (Kepler Release):
+
* Removal for deprecated API implemented with [https://bugs.eclipse.org/bugs/show_bug.cgi?id=401179 bug 401179]
 
+
* Support for Eclipse Galileo (3.5) as we are no longer testing against this platform.
n/a
+
* Support for Windows XP as we are no longer testing against this platform.
 +
* Support for RAP 1.5 (see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=391198 Bug 391198] for details).
  
 
== Bugzilla Tickets ==
 
== Bugzilla Tickets ==
  
* Tickets in [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;target_milestone=3.9.0%20Kepler;product=Scout Scout 3.9.0]
+
* Tickets in [https://bugs.eclipse.org/bugs/buglist.cgi?classification=Technology&columnlist=bug_status%2Ccomponent%2Cresolution%2Ctarget_milestone%2Cbug_severity%2Cshort_desc%2Cchangeddate%2Cop_sys%2Cassigned_to&component=Scout&component=Scout%20SDK&list_id=4141852&product=Scout&query_format=advanced&target_milestone=3.9.0%20Kepler&target_milestone=3.9.0%20M2&target_milestone=3.9.0%20M3&target_milestone=3.9.0%20M4&target_milestone=3.9.0%20M5&target_milestone=3.9.0%20M6&target_milestone=3.9.0%20M7&target_milestone=3.9.0%20RC1&target_milestone=3.9.0%20RC2&target_milestone=3.9.0%20RC3&target_milestone=3.9.0%20RC4&query_based_on= Scout 3.9.0]
  
 
== Target Environment  ==
 
== Target Environment  ==
 
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:  
*Eclipse Galileo (3.5) Limited support only: Scout Web UI (RAP) is not supported.
 
 
*Eclipse Helios (3.6)  
 
*Eclipse Helios (3.6)  
 
*Eclipse Indigo (3.7)  
 
*Eclipse Indigo (3.7)  
Line 52: Line 51:
 
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 66: Line 65:
 
  |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 127: Line 121:
 
*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]]. API Compatibility rules are described in the [[Scout/Coding_Guidelines|coding guidelines]].
  
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
+
 
+
==== +1 Day====
+
# Update build.properties to lastest eclipse milestone versions (e.g. 4.2_eclipseFileName=eclipse-SDK-4.2M5-win32.zip)
+
# Test scout with latest eclipse version
+
 
+
==== Milestone Build ====
+
# configure build.properties file for the corresponding branch/trunk:
+
#* update milestone version: versionMilestone=M5 (N for nightly, RC for RCs)
+
#* scoutRepositoryFolder: version/Release Version (e.g. releases/3.8/3.8.0, nightly)
+
#* make sure rapStaging.target is set to staging updatesite
+
# create a Tag for the corresponding branch/trunk, e.g. 2012-01-31_S-3.8.0M5
+
# reset build.properties for nightly build
+
# run hudson build with the tag created before:
+
#* properties N für nightly, S für stable
+
#* choose tag. e.g. tags/2012-01-31_S-3.8.0M5 or trunk
+
# Test updatesite with empty eclipse
+
# Change Aggregator properties (Check out CVS: extssh:dev.eclipse.org:/cvsroot/callisto) to point to the new build in cvs property file: /cvsroot/callisto/org.eclipse.juno.build/scout.b3aggrcon
+
#* always use the gui editor when adding features and verify the change
+
#* make sure the versionRange is correct
+
#* update location <repositories location=
+
#* checkin (triggers aggregator build)
+
# Test the build
+
# cleanup unnecessary old builds: remove from updatesite releases/3.8/3.8.0/compositeArtifacts.jar and compositeContent.jar
+
# Review the [http://build.eclipse.org/juno/simrel/reporeports/ reports]
+
  
 
== Ramp down Policy ==
 
== Ramp down Policy ==

Latest revision as of 10:20, 2 June 2013


Scout
Wiki Home
Website
DownloadGit
Community
ForumsBlogTwitter
Bugzilla
Bugzilla

Contents

[edit] Eclipse Scout (Kepler Release)

ScoutIcon32c.jpg

This Wiki page is to cover the relevant aspects to fulfill the release review as described here for Eclipse Scout release 3.9 (Kepler).

  • Eclipse Scout is a mature and open framework for modern, service oriented business applications.
  • Scout comes with multi-frontend support for desktop (Swing and SWT), web, and mobile/tablet clients.
  • 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.

Useful Links

[edit] Scout Release Review Documentation

[edit] New and Noteworthy

New and Noteworthy

[edit] End-of-Life

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

[edit] Bugzilla Tickets

[edit] 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:

  • Microsoft Internet Explorer 9
  • Mozilla Firefox 9
  • Google Chrome 16
  • Apple Safari 5


[edit] Mac OSX and JDK1.7

With MacOSX there is a Problems with SWT/AWT Bridge in JDK1.7. See following Bugs: NSView-based implementation of sun.awt.EmbeddedFrame, SWT_AWT bridge broken by openjdk 1.7.0_04ea.

[edit] 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. API Compatibility rules are described in the coding guidelines.

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

[edit] 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.

[edit] Build Process

[edit] 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.

[edit] 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.

[edit] Current Project Metrics

project metrics for Eclipse Scout provided on [ohloh]

[edit] Previous Release Documentation