We are moving to a model that will involve the community more often in the releases for all that wish to be involved. All you got to do is sign up for Gitlab and then jump in wherever you want. So here is the process:

- Reporting of bugs and feature requests
This can be done by anyone with an account. If your feature request is against an existing module, report the 'Issue' there. If there isn't a module yet, report in to the 'Feature Request' project at the root

- Building solutions or fixing bugs
Once you have a bug or feature request and if you have the skills, check out one of our projects and clone it to your own account. Then you work on the code and then send in a 'Merge Request'. If you want to start an open source project based on one of the 'Feature Requests' just contact us or make a comment on the 'Feature Request' and we can stand up the app. If you want to set up a sandbox environment for app- packages for ClearOS 7, you can go here to get started: https://docs.clearos.com/en

- QA and solution promoting
Not a programmer? That's ok, you can help us perform Quality Assurance on upcoming fixes. When a developer builds a package, they can mark the 'Issue' with the 'QA Test' label to tell the community that it is time to test a patch. Patches are typically built into the repo 'clearos-updates-testing'. You can then update the package and give us feedback.

We are broadly implementing Continuous Integration methods within ClearOS. At this stage, you should be able to see a build of a package right when it is committed to Gitlab. You can alternately download the package there as well. This works when just testing commits without pushing the packages to the mirrors.

So the anatomy of the release is like this:

1) make sure you have an 'Issue' on file for all improvements and merges you make. This way you can link the community into your thought process
2) development of package done with commits to 'master' branch
3) once you are willing to publish, package is merged into the 'clear7' branch
4) if the version has been bumped in the spec file (and info.php in the deploy folder for apps) then the system will build it
5) if you merge your commit to 'clear7' the koji build system will pick up your package and attempt to build it. You can watch the progress here: http://koji.clearos.com/koji/
6) packages built in koji will automatically replicate to 'clearos-updates-testing'. You can pick them up with a 'yum --enablerepo=clearos-updates-testing install <packagename>'

Also. Thanks for all your help over the years and your continual support of ClearOS.