FESA3 2.0.1 Release Planning

FESA FWK

• sync with CERN code base, last release of FWK v2.1.0 containing bug fixes from 19.08.2014?
  • no synchronization with latest release @CERN will be performed, a part of the bugfixes will be integrated anyway
  • the released version @GSI will be 2.0.1
• integration of cmw-rda3 (using zeromq)
  • done by A in a local installation
• extension of core / code generation for cmw-rda3
  • done by A in a local installation
• update / extension of tests
  • adaption of the core-integration-tests for GSI -> A
  • extension of googletest suites to provide a common base class for middleware access -> A
  • the core-integration-tests copied from CERN for release 1.0.0 were not updated since that time, only the most important tests of these tests will be updated for the upcoming release -> A details see README in project fesa-core-integration-test/testbed-testsuite
• integration of new python code generation
  • core
  • gsi - done by A in a local installation
• extended GSI Template for FESA classes
  • new: Device Description Property -> A
  • extension of GSITemplateIntegrationTest suite for a test of the new device description property -> A
  • not realized for the upcoming release: documentation of the new device description property TODO September 2014 -> A
• integration of Harald's cern-timing library -> S
• GSI's beam process concept integration
  • work in progress -> A , details and example: see README in fesa-core-gsi-integration-test/WRTImingTest
• White Rabbit timing event definition update -> Jutta, KW 35, integrated in FESA3 FWK -> S,
• possibility to define White Rabbit events locally??? WIKI documentation
  • to provide by A in September 2014
• update of documentation
  • TODO September 2014 -> A
• adaption of unit tests for the core ?
• test of local development version, e.g according to relevant parts of the test plan
  • test of the local installation -> A for 32Bit
• update of migration script for migrating classes / deploy-units / instantiation documents from 1.x.x to 2.x.x
  • provide a script for migration from FESA 1.3.1 to FESA 2.0.1 -> A
  • provide WIKI documentation accordingly -> A
• availability of a release branch for RPM builds: Fr, 22.08.14 prepared by A before his holiday.

• long term, new release: integration of CMX metrics for runtime diagnostics, requires infrastructure for additional tools -> SV group

FESA Explorer

• latest FESA Explorer -> Harald
  • version in trunk can be used for new release according to Harald
  • TODO: WhiteRabbit based timing integration, possible with WR timing event list
  • the latest FESA Explorer will probably not be backwards compatible to FESA 1.x software

RPM Installation

• usage of common buildsystem for CMW and FESA -> S,
• reflection of the python code generation in the RPM spec files -> S,
• realization of new installation structure as discussed and described on https://www-acc.gsi.de/wiki/FESA/FESA3RPMInstallation#Installation_Structure -> S,
• integration of new cern-timing library (additional RPM packet) after successful test -> Harald, Test , -> S,
• integrate latest FESA Explorer -> Harald, version in trunk,
• test of RPM installation according to test plan -> S, ; A:
  • test installation on virtual machine used to build RPM packets -> S,
  • test installation on asl cluster according to test plan -> S, ; A:

FESA Eclipse plug-in

• integration of bug fixes (table editor, etc) , -> S,
• provide an installation of Eclipse plug-in via update site, -> S,
  • currently without DB integration
• tests according to test plan-> S,
• new: changelog for new projects, automatic include path detection/C++ indexer settings, support for class association,
• ...
• long term: Integration FESA Datenbank -> ongoing discussions, end of 2014 or next verseion of FESA3 Eclipse plug-in
• long term: usage of Eclipse Luna / JAVA8 -> end of 2014

FESA Environment

• new WIKI pages for the latest release including, -> S / September: -> A
  • installation, setup information for developers -> S,
  • updated C++ code snippets -> A
  • updated internal FESA documentation, September: -> A, wiki

FESA FECs

• as mentioned by Harald: update of libraries for FECs required (replacement of omniORB etc)
  • Solution to avoid version clashes: FESA3 binaries include their required libraries statically to avoid version clashes (e.g. with boost libraries)
  • Existing libraries will be kept for backwards compatibility with previous releases

Post-Release

• run post install script to copy the configuration files, -> S,
• update Linux MOTD in development cluster, -> S,
• inform cosylab, put RPM packages + eclipse plu-in update site files on webdavs://www-acc.gsi.de/dav/fesa-release-2.0.1 for download, -> S,
• update MCS, -> S, *