Skip to main content
Jump to: navigation, search

Difference between revisions of "Papyrus/2018.9 Work Description"

(User Experience)
(Rules about gerrit that will added in rules and charter)
Line 19: Line 19:
 
===Rules about gerrit that will added in rules and charter===
 
===Rules about gerrit that will added in rules and charter===
  
* Verify headers
+
* Verify headers, bug number,  commiter (name not mandatory, but companies), verify dates, ( rules with "," or "-")
* Verify javadoc
+
* Verify javadoc that means something.
 
* Verify  Non-NLS
 
* Verify  Non-NLS
* Verify  tags (@since, ...)
+
* Verify  tags (@since plugin-number, ...)
* Verify  version number
+
* Verify  version number (API tools)
 
* Avoid re-export of plug-ins
 
* Avoid re-export of plug-ins
* There is no order of methods in a class (do not take in account visibility or name of methods)
+
* There is no order of methods in a class (do not take in account visibility or name of methods), not the order of keyword.
 
* It is not mandatory to have only one returns per method
 
* It is not mandatory to have only one returns per method
* All attributes must be at beginning of the class
+
* All attributes, field must be at beginning of the class
 
*
 
*
 
*Next step coding rules
 
*Next step coding rules

Revision as of 05:48, 2 July 2018

This page is a draft of the roadmap for the ongoing release of Papyrus for the 2018.09 simultaneous release, planned for september 2018. Please fill free to comment the listed tasks or to interact on the Papyrus mailing list if you have any feedback on the content of this page.

All the work realized by CEA LIST is sponsored by CEA LIST, Esterel, Airbus Defence and Space.


All bugs, or feature may be found in the tracker [1]

User Experience

  • Diagram: improve sequence diagram combined fragment + observation and general ordering
  • Toolsmith tool: improve Facet editor
  • layer: add it into the model explorer, refactoring layer model + generation, property view
  • diagram generation: improvement.
  • improve support of CDO.
  • fix problems about xtext support and language
  • integration of formula on table.
  • continue AF support integration.
  • releng: to fill.

Rules about gerrit that will added in rules and charter

  • Verify headers, bug number, commiter (name not mandatory, but companies), verify dates, ( rules with "," or "-")
  • Verify javadoc that means something.
  • Verify Non-NLS
  • Verify tags (@since plugin-number, ...)
  • Verify version number (API tools)
  • Avoid re-export of plug-ins
  • There is no order of methods in a class (do not take in account visibility or name of methods), not the order of keyword.
  • It is not mandatory to have only one returns per method
  • All attributes, field must be at beginning of the class
  • Next step coding rules

Back to the top