@@ -28,7 +32,9 @@ The develop branch always holds a functional version with the newest features bu
#### Acceptance
This is an internal branch that should not be used by any merchant.
This is an internal branch that should not be used by any merchant. The branch maps the crefopay communication URLs to the CrefoPay QA automated testsystems:
* Production: https://acceptance02.pay-dev.de
* Sandbox: https://devel02.pay-dev.de
#### Hotfix
...
...
@@ -65,3 +71,20 @@ A minor release normally contains some new features.
### Sub-Version
A sub version normally comes up with a hotfix or with some very minor changes; for example some error handling within the code that makes an existing functionality more stable.
## Release Cycle
The normal release cycle is one release per month. The Release date should always be the first half of the first week of a month. If there is a hotfix or feature release depends on the issues and the tasks of the current cycle.
Every release and it's features will be documented within the plugins CHANGENLOG.md and it will be generated a tag for every version that has been pushed to master.
## Quality Assurance
Every release has to pass a predefined set of stages to keep and guarantee the high quality of the plugin. This stages are:
`Develop -> Acceptance -> Master`
Every completed feature can be pushed directly into the develop branch by follow the git flow guidelines. A feature is complete when it's own functionality has been implemented and tested. When a release and it's features are closed and it should be released into master, it will be pushed acceptance. In this context *closed* means that every single feature or hotfix has been pushed to develop branch.
After merging the develop into acceptance branch, the CrefoPay QA department will be informed and they will start their automated and some manual testing.
When QA have finished testing and haven't found any issues, the acceptance/develop branch will be pushed to master. If not already updated at this point, the CHANGELOG.md will be updated and a new tag will announce the new version.
