Project Plan For Papyrus, version 1.0.0

Introduction

This document lays out the feature and API set for the incoming release of the Eclipse Papyrus (MDT Papyrus) Project, version 1.0.0 This project plan inherits from the Modeling Project Plan, which should be referenced when consulting this individual project plan. In addition to the detailed items listed below, the Papyrus team will ensure the maintenance of its existing plug-ins.

Release Deliverables

The release deliverables have the same form as is found in most Eclipse projects, namely:
  • Papyrus source code release, available as versions tagged "1.0.0" in the project's GIT repository.
  • Papyrus SDK (includes runtime, sources, examples, and documentation) (downloadable and update site).
  • Papyrus runtime binary distribution (downloadable and update site).
  • Papyrus stand-alone binary distribution (downloadable).
  • Papyrus tests (downloadable)
  • Papyrus examples (downloadable)

Table of Contents

Release Milestones

Release milestone occurring at roughly 6 week intervals and follow the Platform milestone releases by approximately 3 days; that is, until the final 4.4 release of the Platform, upon which Papyrus and other projects will release simultaneously. As Papyrus is a dependency of numerous other projects, Papyrus will deliver its milestones within three days of the Eclipse Platform. It is anticipated that Papyrus will synchronize its milestones with the Luna milestone schedule.
M108/23/2013
M210/04/2013
M311/15/2013
M412/20/2013
M501/31/2014
M603/14/2014
API Freeze
M705/09/2014
Feature Freeze
RC105/23/2014
RC205/30/2014
RC306/06/2014
RC406/13/2014
Luna06/25/2014
Papyrus will produce maintenance releases to align with the Luna SR releases, that includes the Eclipse Platform 4.4.1 and 4.4.2 releases. Papyrus may produce interim maintenance releases in addition to these in order to satisfy clients requests.
  • Friday, September 27, 2014 - Papyrus 1.0.1 maintenance release (Luna Service Release 1)
  • Friday, February 28, 2015 - Papyrus 1.0.2 maintenance release (Luna Service Release 2)

Table of Contents

Target Environments

In order to remain current, each Eclipse release targets reasonably current versions of the underlying operating environments. The Eclipse Papyrus project depends upon on the Platform and other projects, which are mostly "pure" Java. The 4.4 release of the Eclipse Platform Project is written and compiled against version 6.0 of the Java Platform APIs, and targeted to run on version 6.0 of the Java Runtime Environment, Standard Edition. Papyrus will target Java 6. Eclipse Platform SDK 4.4 will be tested and validated on a number of reference platforms. MDT Papyrus will be tested and validated against a subset of those listed for the platform.

Internationalization

The Eclipse Platform is designed as the basis for internationalized products. The user interface elements provided by the Eclipse SDK components, including dialogs and error messages, are externalized. The English strings are provided as the default resource bundles. As a result, the Papyrus project will provide English strings in its default bundles and be localized to a subset of those locales offered by the Platform. This plan will be updated to indicate which locales will be provided and the time frame for availability.

Table of Contents

Compatibility with Previous Releases

The Papyrus 1.0.0 project will be developed in parallel, and released simultaneously, with the following projects. As stated above, each milestone release of the Papyrus 1.0.0 project will be compatible with the corresponding milestones for each of these projects, and delivered the appropriate offset.
  • Eclipse Platform SDK version 4.4
  • Eclipse Modeling Framework (EMF) version 2.10
  • Model Development Tools (MDT) UML2 version 4.2
  • Graphical Modeling Framework (GMF) version 1.7

Table of Contents

Themes and Priorities

A list of project requirements and agreed upon implementation time frames is found in this document. For the milestones listed in this document, a set of overall themes is used to indicate what major set of functionalities is to be concentrated on for each. These themes are presented below, while the requirements document and associated Bugzilla entries are left to those wanting more detailed information on each.

Editors

This theme addresses issues related the diagram editors of Papyrus. It concerns more precisely all generic features related any kind of Papyrus diagram editor. For the UML2, it concerns following diagram editors: [Class diagram], [Package diagram], [Composite structure diagram], [Component diagram], [Profile diagram], [Use case diagram], [State machine diagram], [Protocol state machine diagram], [Activity diagram], [Sequence diagram], [Communications diagram], [Interactions overview Diagram], [Timing diagram]. For the SysML, it concerns following specific diagram editors: [Activity diagram], [Block definition diagram], [Internal block diagram], [Package diagram], [Parametric diagram], [Requirements diagram], [Sequence diagram], and [State machine diagram].
  • Committed

    • [Table 2] Papyrus Table must provides the API to open Xtext Editor as CellEditor [417915] (target milestone: M4)
    • [Customization] Papyrus shall enable to customize the creation policy of views [399860] (target milestone: M7)
    • [General] Papyrus shall enable to model UML Constraints. [322933] (target milestone: M6)
    • [OCL] Papyrus shall provide an advanced OCL Support. [399868] (target milestone: M7)
    • [SysML Parametric Diagram] Papyrus shall provide a parametric diagram editor. [297816] (target milestone: M4)
    • [Table 2] The edition of the cell must be on Double Click and not on single click [426693] (target milestone: M7)

Extensibility

This theme addresses the need for extensiblity improvements of the MDT Papyrus implementation and APIs. It concerns more precisely all features related to following concerns: [Backbone] and [Metatooling].
  • Committed

    • [EMF Facet] Papyrus should progressively support EMF Facet 0.2 [386118] (target milestone: M7)
    • [All Diagrams] Papyrus shall provide configurable modelling assistants [399871] (target milestone: M4)
    • [Palette customization] Papyrus shall support pre-defined references in the Palette customization [417838] (target milestone: M2)
    • [UI Customizability] Papyrus shall provide a customizable "New Child" menu within model explorer view [351803] (target milestone: M4)
    • [Property View] Improvement of inheritance of property view generation [428423] (target milestone: M7)

Scalability

This theme addresses the need for scalability and performance improvements of the MDT Papyrus implementation and APIs.
  • Committed

    • [Tests - Performances] Papyrus shall provide a test bench for performance evaluation [399874] (target milestone: M4)

Usability

This theme addresses the need for usability improvements of the MDT Papyrus implementation and APIs. It concerns more precisely all features related to following concerns: [Palette], [Property View], [Model Explorer], [Sash Editor], and [Team Working].
  • Committed

    • [Usability] Papyrus shall provide a copy/paste/cut feature [290261] (target milestone: M7)
    • [Table 2] export table as image - how to? [417095] (target milestone: M4)
    • [Table 2] Table must provide a row filter located in the column header [408930] (target milestone: M7)
    • [Table 2] Create/Destroy Axis dialog must provides a check box to show/hide inherited properties [411026] (target milestone: M5)
    • [Table 2] The user must be able to sort rows selecting columns headers [414124] (target milestone: M4)
    • [CSS] The CSS Engine shall support compartments (Show/Hide, collapse, show title...) [417178] (target milestone: M2)
    • [CSS] The CSS Engine shall support element visibility [417180] (target milestone: M2)
    • [CSS] The CSS Engine shall support label visibility & mask [417396] (target milestone: M4)
    • [CSS] The CSSEngine shall support attribute selectors for references typed with NamedElement [417846] (target milestone: M2)
    • [CSS] Project shall have a property for associating project style sheets [429643] (target milestone: M7)
    • [CDO] Support controlled resources and lazy loading [415369] (target milestone: M2)
    • [CDO] Model search in repository models [415371] (target milestone: M2)
    • [CDO] External document linking [415373] (target milestone: M2)
    • [CDO] Model repository administration [415375] (target milestone: M3)
    • [Model / CSS] Add properties view to define Model's stylesheets [429642] (target milestone: M7)

Documentation

This theme addresses the need for documentation of the MDT Papyrus implementation and APIs. It concerns more precisely all features related to following concerns: [Documentation - User], and [Documentation - Developer].
  • Committed

    • [Table 2] The advanced user must be able to define his own table kind [400792] (target milestone: M7)
  • Deferred

    • [CDO] Programmer's Guide for CDO integration [415392] (target milestone: ---)

Miscellaneous

This theme addresses all tasks that may not be included in one of the previous theme.
  • Committed

    • [Core - ModelSet] Improve the resource handling in ModelSet [406234] (target milestone: M6)
    • [Resource Management] Refactoring of the 3-files model and PageManager [429239] (target milestone: M6)
    • [General] Papyrus shall provide a read only mode [323802] (target milestone: M6)
    • [Widgets / Transactions] Papyrus dialogs should be transactional [402525] (target milestone: M6)

Eclipse Compatibility

this theme adresses the support and compatibility with platform 4.X and 3.X
  • Committed

    • [UML 2.5] Migrate Papyrus to UML 2.5 [429744] (target milestone: M6)

Table of Contents

Appendix Legal Notices

  • Java is a trademark or a registered trademark of Sun Microsystems, Inc.
  • UML, SysML and OMG are trademarks or registered trademark of the Object Management Group, Inc.
  • All other products or company names are mentioned for identification purposes only, and may be trademarks or service marks of their respective owners.

Table of Contents

view raw xml of project plan
from project meta-data key "projectplanurl"