From OpenSCADAWiki
- State: Initiation
The common releasing process for the users to estimate your expectations and for the developers to remind the tasks:
1. The preparing and building week:
- Building the last Work SVN-revision for all environments of the irregular building to provide early and wide testing the coming LTS release.
- Announcing the releasing process start:
- creating a new release page or update page on the Wiki;
- creating a new news-page on the OpenSCADA site.
- Merging the Work branch changes or copying the whole Work branch tree to the LTS branch-tree.
- Making some LTS specific changes about the version rise:
- updating configure.ac for version of the release-update and core library;
- updating data/*.spec and data/{debian,debian_mod}/changelog for the new version number and appending the files' changelog for new release-update entry.
- Forming-appending the LTS ChangeLog by the changes from the Work ChangeLog, grouping the changes by the location and sorting them by the fixing status and the level, with combination new features under one item and without removing any different changes.
- Copying the significant changes from the formed LTS ChangeLog to the related page of the release-update, taking the changes in the level more or even than "!!".
- Translating the release-update page(s), updating the ToDo and RoadMap.
- Generating the actual offline documentation using the service procedure "EXT: Off-line documentation".
- Committing the LTS tree changes to the repository and building that.
2. The testing and post-building week(s):
- Updating the Download page.
- Announcing the release-update, also on FaceBook and LinkedIn.
- Hot testing the release build.
- Finishing and fixing the ChangeLog translating and the documentation.
- Generating the actual offline documentation using the service procedure "EXT: Off-line documentation".
- Committing the release fixes to the repository and building that for the second build, and for each week of appearing critical fixes — the first week without the critical fixes means the final of the LTS releasing, so, USERS — test closely the LTS release for do not complain to its final build!
- Updating binary copies of standard OpenSCADA libraries: OscadaLibs.db, VcaBase.db, VcaElectroEls.db.
This update of the 0.9 LTS release fixes about 60 bugs and appends some improvements, which you can read wholly in the update ChangeLog.
The key features of the update are:
1 OpenSCADA libraries and projects
- LibsDB.OscadaLibs: The Devices Library appended for the protocol IEC-62056 implementation (DevLib.IEC62056). The offline documentation appended for the document "AGREEMENT ON TECHNICAL SUPPORT OF THE "OpenSCADA" SOFTWARE" version 2 and the new module DB.DBGate.
- FIX:LibsDB.vcaBase.Main.alarmsSt: Some fixed for the original messages and the "quietation" completly replaced by "confirmation". Restored in preventing the duplicate entries for new alarms in that category.
2 API
!!!!:Changes:
- SYS: The station statuses unified in the function isRunning(), isFinalKill() and stopSignal(). TCfg::setReqKey() appended by a new argument "treatDep".
- DB: dataSeek(),dataGet(),dataSet(): Expanded for the local configuration context argument "localCfgCtx";
- *,DB: TBDS::dataSeek() and TTable::fieldSeek() switched to the seek cache implementing in the corresponded modules.
Appends:
- TMess,DB,DB.{SQLite,MySQL,PostgreSQL,FireBird}: TMess appended for a function of detection the configuration translation translCfg(), which used in all DB modules and in dataSet().
- SYS: Appended for the global configuration context accessing functions cfgCtx() and setCfgCtx().
- The loading and saving configuration appended for own lock TSYS->cfgLoadSaveM().
- Appended for the function pathLevEnd() of the paths processing from the end.
- TRegExp: Appended by the function getPattern().
- TFld: Appended for the combined string variant of the length field - lenS().