User Tools

Site Tools


for_developers:releases

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
for_developers:releases [2019/01/16 19:47]
kunz update information to conform with release and deployment management
for_developers:releases [2019/01/30 11:04] (current)
kunz Add link and fix typos
Line 1: Line 1:
 ====== Releases ====== ====== Releases ======
  
-EEROS is released in the form of the source code via Github. All releases are found [[https://​github.com/​eeros-project/​eeros-framework/​releases|here]]. ​+EEROS is released in the form of the source code via GitHub. All releases are found [[https://​github.com/​eeros-project/​eeros-framework/​releases|here]]. ​
  
 The release workflow supports multiple active releases. Every active release has its own release branch. The actual release commit is tagged with the version number. EEROS is versioned according to the [[https://​semver.org/​|Semantic Versioning Specification]]. The first major version of EEROS for example, has the tag v1.0.0. The release workflow supports multiple active releases. Every active release has its own release branch. The actual release commit is tagged with the version number. EEROS is versioned according to the [[https://​semver.org/​|Semantic Versioning Specification]]. The first major version of EEROS for example, has the tag v1.0.0.
Line 7: Line 7:
 The releases which are not supported anymore will still be accessible over their tags. The branches were deleted since the versions shouldn'​t be used anymore. The releases which are not supported anymore will still be accessible over their tags. The branches were deleted since the versions shouldn'​t be used anymore.
  
-The development is done with the workflow **"​develop with a fork"​**. For contribution,​ EEROS must be forked. The implementation is done in the fork. Afterwards, the changes are merged into the master branch of the main repository. The merge is initiated by the pull request feature of Github. This workflow allows an easy way to contribute for everyone. It also improves the code quality since the pull requests are reviewed before the merge.+The development is done with the workflow **"​develop with a fork"​**. For [[for_developers:​contribute|contribution]], EEROS must be forked. The implementation is done in the fork. Afterwards, the changes are merged into the master branch of the main repository. The merge is initiated by the pull request feature of GitHub. This workflow allows an easy way to contribute for everyone. It also improves the code quality since the pull requests are reviewed before the merge.
  
 Therefore, the current snapshot of EEROS with the latest features is accessible on the master branch. Therefore, the current snapshot of EEROS with the latest features is accessible on the master branch.
    
for_developers/releases.txt · Last modified: 2019/01/30 11:04 by kunz