From 886bfcc4e3c41fd367928b52ef3245d8fcdca5ae Mon Sep 17 00:00:00 2001 From: jaapjansma <jaap@edeveloper.nl> Date: Thu, 25 Jun 2020 09:33:21 +0000 Subject: [PATCH] Update README.md --- README.md | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 56d6e41..ed38e1f 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,30 @@ # form-processor - - The form processor extension gives you the ability to define business logic for handling form submissions. A form submission could come from the CiviMRF, external system or just a direct submission. -[See **wiki** for more information](https://lab.civicrm.org/jaapjansma/form-procesor-designer/wikis/home). +[See **docs** for more information](https://docs.civicrm.org/formprocessor/en/latest/). The extension is licensed under [AGPL-3.0](LICENSE.txt). +## Contributing + +Feel free to contribute to this extension. Create a Merge Request and also add a little description to CHANGELOG.md of what you have changed + +## Releasing Process + +When one of the admins think it is time to relase a new version they might do so. You can also ask them to release a new version. +Usually this when the release is being tested and put in production. + +For admins creating a release those are the steps to follow: + +1. Update info.xml to reflect the new version number and release date +2. Remove the 'not yet released' from CHANGELOG.md +3. Copy the changes +4. Go to tags, create a new tag and paste the changes +5. After that update info.xml to add a new version number ending with _-dev_ +6. Update changelog add a heading for the new version with the text _not yet released_ + ## Requirements * PHP v5.4+ -- GitLab