Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "JWT Checklists"

(Release JWT Workflow Editor)
Line 3: Line 3:
  
 
== Release JWT Workflow Editor ==
 
== Release JWT Workflow Editor ==
 
* update readme
 
* update docs (about, package.html)
 
* update keybindings
 
* update javadoc
 
* update extension point description
 
* valid licence information
 
* adapt converter for new version
 
* close finished bugs, move open ones to next release
 
* CVS: new tag, deploy
 
* update copyright year information
 
* adjust plugin*.properties translations
 
* remove unneccessary dependencies
 
  
 
=== Preparing ===
 
=== Preparing ===
 +
 +
* Make sure the copyright/year information in the Java headers is up to date
 +
* Adjust plugin*.properties translations
 +
* Remove unneccessary dependencies using the Plugin.xml editor
 +
* Make sure the description of the JWT extension points is up to date
 +
* Close finished Bugzilla tasks and move open ones to next release
 +
* Update the internal documentation in JWT-WE (about.txt, package.html)
 +
* The converter must be updated to the newest file format
 +
* Ensure that all keybindings for Eclipse commands (menu/toolbar) are set correctly
 +
* Make sure the licence information is valid
 +
* The internal readme file must be up to date
  
 
=== Generating Packages ===
 
=== Generating Packages ===
 +
 +
* Generate new Javadoc
 +
* Generate a release package and a source package for the Workflow Editor
 +
* Generate a release package and a source package for the WE View Creator
 +
* Generate release and source packages for all WE Plugins
 +
* Update the example processes and create a ZIP archive
 +
* Sign packages
  
 
=== Deploying ===
 
=== Deploying ===
 +
 +
* Tag the release state on the CVS as a new version
 +
* Archive old release and upload new release packages to the download server
 +
* Update the Wiki download page and related Wiki pages
 +
* Update the Eclipse JWT page
 +
* Adapt the feature in the JWT Eclipse Update Site
  
 
== Release AgilPro LiMo and Simulator ==
 
== Release AgilPro LiMo and Simulator ==

Revision as of 13:22, 27 July 2008

Overview

Release JWT Workflow Editor

Preparing

  • Make sure the copyright/year information in the Java headers is up to date
  • Adjust plugin*.properties translations
  • Remove unneccessary dependencies using the Plugin.xml editor
  • Make sure the description of the JWT extension points is up to date
  • Close finished Bugzilla tasks and move open ones to next release
  • Update the internal documentation in JWT-WE (about.txt, package.html)
  • The converter must be updated to the newest file format
  • Ensure that all keybindings for Eclipse commands (menu/toolbar) are set correctly
  • Make sure the licence information is valid
  • The internal readme file must be up to date

Generating Packages

  • Generate new Javadoc
  • Generate a release package and a source package for the Workflow Editor
  • Generate a release package and a source package for the WE View Creator
  • Generate release and source packages for all WE Plugins
  • Update the example processes and create a ZIP archive
  • Sign packages

Deploying

  • Tag the release state on the CVS as a new version
  • Archive old release and upload new release packages to the download server
  • Update the Wiki download page and related Wiki pages
  • Update the Eclipse JWT page
  • Adapt the feature in the JWT Eclipse Update Site

Release AgilPro LiMo and Simulator

AGILPRO(LiMo+Sim):

  • update release notes
  • update tutorial
  • update javadoc
  • update howtos
  • update install informations
  • valid licence in installer?
  • valid update splashscreen?
  • copy emf model to simulator
  • convert sample processes
  • test installer for all operating system versions
  • SVN: branch, javadocs
  • CVS: tag version
  • mylyn: close finished bugs, move open ones to next release

Preparing

Generating Packages

Deploying

See also

Back to the top