Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Scout/Release/JunoDoc"
(→End-of-Life) |
(→Bugzilla) |
||
Line 49: | Line 49: | ||
== Bugzilla == | == Bugzilla == | ||
− | * Status: | + | * Status: OK, ticket transfer from internal tickets completed |
* No open major, critical, or blocker | * No open major, critical, or blocker | ||
* Link to list of all Scout tickets [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;product=Scout Scout tickets] | * Link to list of all Scout tickets [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;product=Scout Scout tickets] |
Revision as of 10:48, 22 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:
- 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 diffent frontend technologies (Swing, SWT, Web) without any changes in the source code
- It 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
See the Eclipse Scout 3.8.0 New & Noteworthy
Non-Code Aspects
Scout Documentation/Tutorials etc. provided on the Scout wiki
Status per communication channel
- Forum: OK
- Wiki: OK, redesign pending
- Webpage: OK, redesign pending
- 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
- Status: OK, ticket transfer from internal tickets completed
- No open major, critical, or blocker
- Link to list of all Scout tickets Scout tickets
Schedule
Our initial schedule was presented at EclipseCon 2010 with the following goals:
- Project status by April 2010
- Jasper integration by EclipseSummit 2010
- Birt integration by EclipseSummit 2010
- Wicket integration by EclipseCon2011
- Indigo Release train
Except for the Birt integration, these goals have been met with demonstrations at talks at the EclipseSummit/EclipseCon.
Community and Support
Activities 2010
- Meeting Riena Team in Frankfurt
- EclipseCon: Lightning Talk, Booth, (sponsored) Tutorial
- Eclipse Banking Day Copenhagen: Talk
- Eclipse Stammtisch Karlsruhe: Talk
- Eclipse Summit: Talk in RT Tutorial, Booth
- Eclipse Day Paris
Activities 2011
- Meeting RAP in Karlsruhe
- EclipseCon 2011: Tutorial, Booth, two (sponsored) Talks
- Article in EclipseMagazin 3.11
- Meeting Code Recommenders in Darmstadt
- Eclipse Webinar 17.5.2011
- Demo Camp Darmstadt: Talk (planned)
Current Status
Observing from forum/bugzilla there adoption is starting. So far, contributing to Scout outside of BSI has not yet been observed. All committers are currently employees from BSI.
IP Issues
Link to Scout IP Log
IP Log was approved on 30.05.2011 @21:37
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]