From OpenSCADAWiki
(Updating to match new version of source page) |
|||
| Line 3: | Line 3: | ||
{{Info|* '''Автор:''' [[User:RomanSavochenko|Роман Савоченко]]}} | {{Info|* '''Автор:''' [[User:RomanSavochenko|Роман Савоченко]]}} | ||
</noinclude> | </noinclude> | ||
| − | + | The common releasing process for the users to estimate your expectations and for the developers to remind the tasks:<br/> | |
| − | {{CntHdr|1. | + | {{CntHdr|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 [[Special:MyLanguage/Documents|release page]] or [[Special:MyLanguage/Documents/Release_0.9|update page]] on the Wiki; |
| − | ** | + | ** creating a new news-page on the [http://oscada.org/en/main/|official 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 [[Special:MyLanguage/Works/To_do|ToDo]] and [[Special:MyLanguage/Works/Road_map|RoadMap]]. |
| − | * | + | * Generating the actual offline documentation using the service procedure "[[Special:MyLanguage/Libs/Service_procedures#docOffLine|EXT: Off-line documentation]]". |
| − | * | + | * Committing the LTS tree changes to the repository and building that. |
| − | + | ||
| − | + | ||
| − | {{CntHdr|2. | + | {{CntHdr|2. The testing and post-building week(s):}} |
| − | * | + | * Announcing the release-update, also on [https://www.facebook.com/Roman.Savochenko FaceBook] and [https://www.linkedin.com/in/roman-savochenko-71b50272/ LinkedIn]. |
| − | * | + | * Hot testing the release build. |
| − | * | + | * Finishing and fixing the ChangeLog translating and the documentation. |
| − | * | + | * Generating the actual offline documentation using the service procedure "[[Special:MyLanguage/Libs/Service_procedures#docOffLine|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 the LTS releasing, so, USERS — test closely the LTS release for do not complain to it final build! | ||
Revision as of 09:49, 28 February 2025
- Автор: Роман Савоченко
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):
- 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 the LTS releasing, so, USERS — test closely the LTS release for do not complain to it final build!