RYS soecifics

parent 495bd074
......@@ -204,12 +204,28 @@ Check for it with `ruby -wc PATH_TO_FILE`. In orders to check all files :
find . -name "*.rb" -type f -exec ruby -wc {} \; | grep -v OK
```
##### Versioning
### RYSy
All our RYSy are versioned by semantic versioning. For details please see https://semver.org/#semantic-versioning-200
This topic explain some RYS specific dev requirements. What is RYS you can see in full documentation - can be found [on project's wiki](https://github.com/easysoftware/rys/wiki).
1. level - MAJOR - includes changes which are release specific - lots of changes, refactoring and whole new features, migrations and etc.
#### Versioning
2. level - MINOR - includes new small features, migrations, minor change of internal logic
All our RYSy are versioned by semantic versioning. For details please see [https://semver.org/#semantic-versioning-200](https://semver.org/#semantic-versioning-200)
3. level - PATCH (or bug-fix) - its only for bug-fixing or harmless changes, such as documentation, readme, etc. ! This version must not include migrations and breaking chagnes !
3. level - MAJOR - includes changes which are release specific - lots of changes, refactoring and whole new features, migrations and etc.
4. level - MINOR - includes new small features, migrations, minor change of internal logic
5. level - PATCH (or bug-fix) - its only for bug-fixing or harmless changes, such as documentation, readme, etc. ! This version must not include migrations and breaking chagnes !
#### Release cycle
In RYS repositories there are always 2 protected branches - `master` and `devel`.
Our idea is that `master` branch contains stable version of RYS, which is in production (clients application have `~>` for this version). `devel` instead is branch for future features.
Distribution of RYS engines is done by our gems server ([http://gems.easysoftware.com](http://gems.easysoftware.com)). You can push to this server new version of RYS only by following rules:
2. production release is merged to `master` branch, there is properly CHANGELOG and version of RYS is increased.
3. when you need pre-release feature branch, you always need to use `beta`version + its a MAJOR version change
......@@ -8,6 +8,30 @@ RYS engines are separated to few gems, and source code is on github. So for full
https://github.com/easysoftware/rys
## DEV guide of RYS
#### Versioning
All our RYSy are versioned by semantic versioning. For details please see [https://semver.org/#semantic-versioning-200](https://semver.org/#semantic-versioning-200)
3. level - MAJOR - includes changes which are release specific - lots of changes, refactoring and whole new features, migrations and etc.
4. level - MINOR - includes new small features, migrations, minor change of internal logic
5. level - PATCH (or bug-fix) - its only for bug-fixing or harmless changes, such as documentation, readme, etc. ! This version must not include migrations and breaking chagnes !
#### Release cycle
In RYS repositories there are always 2 protected branches - `master` and `devel`.
Our idea is that `master` branch contains stable version of RYS, which is in production (clients application have `~>` for this version). `devel` instead is branch for future features.
Distribution of RYS engines is done by our gems server ([http://gems.easysoftware.com](http://gems.easysoftware.com)). You can push to this server new version of RYS only by following rules:
2. production release is merged to `master` branch, there is properly CHANGELOG and version of RYS is increased.
3. when you need pre-release feature branch, you always need to use `beta`version + its a MAJOR version change
# Lukas's personal workflow
How to start develop with RYS? There are some of my recommendations...
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment