== Timeline ==

The [wiki:testplan ProMoT test plan] describes testing procedures to ensure that new releases of ProMoT do not break existing functionality. 

== General Steps ==

 * Test core functionality (see [wiki:testplan])
 * Test functionality given in publication (see [http://dx.doi.org/doi:10.1093/bioinformatics/btp029 paper]) 
 * Update [source://Promot/trunk/promot/BUGS.txt BUGS.txt]
 * Update [source://Promot/trunk/promot/VERSIONS.txt VERSIONS.txt]
 * Update [source://Promot/trunk/promot/licences.txt licences.txt] (no changes)
 * Update Windows version
 * Update [source://Promot/trunk/promot/doc/tutorials/ tutorials]
 * Update [source://Promot/trunk/promot/doc/mdl-guide manual]
 * Update [http://www.mpi-magdeburg.mpg.de/projects/promot/ ProMoT website]
 * Announce new ProMoT version on
   * [http://www.sbml.org/ SBML.org]
   * [http://www.openwetware.org/ OpenWetWare.org]

== Todo ==

=== Version 0.8.2 ===

 * Bugs without tickets, to be addressed before release

 * ~~explorer: parent.ignore_in_export is ignored (string instead of expected boolean)~~ [[BR]] ''Should be ok now, see [8242].''

 * ~~editor: link-in disabled (use of strong terminal within module, cmp. ticket #131) 
  needs to be checked again if disable is still necessary/needed~~ [[BR]] ''Should be ok now, see [8244].''

 * updates in kb finished? [[BR]]
   * ''Do you mean "icons for executable models? See [8165]. The rest of the models in kb were changed when executable model is straight forward.''
   * flip variables are exported (contrary to logical models) which is clearly not desirable (introduces ~800 additional vars for egf compare to 600 original vars)
   * deprecated elements in logical (example) models

 * updates of documentation?
 * We need some logical dir structure for ProMoT versions in /dist/. What to do with 0.8.0, 0.8.1, 0.8.2?

 * fix failing junit tests for !VizExplorer (all tests for !AttributeReaderTest + !LogicalNetworkParser fail with NPE as PromotUI.UI seems to be null)
 
=== Version 0.9 ===

improve stability

  * improve test coverage
  * develop concept concurrency issues
  * solve some concurrency issues as prove of concept