RFC : Version Release and Community Testing Process
We have been discussing version releases and testing for the forthcoming 3 month community roadmap process.We don't have a QA team so we need to find a good way to test features with the community before pushing out to deployed instance and merging with the master repo.
This process is proposed as follow, please comment:
- the Editoria lead dev (@alexgeo) will develop each new feature on a new branch. For those that don't know what a branch is just think 'copy' - it allows us to build features on a copy without yet touching the main code base.
- when the feature is ready the lead dev will merge the feature branch into a staging branch.
- when this merge to the staging branch occurs it will trigger an automatic deployment of that code to a stable url (perhaps editoria-staging.coko.foundation)
- the community can then test the feature on this branch and look for bugs or suggest improvements / call out where the feature is not what was proposed or is not acting as expected
- the lead dev makes relevant changes, re-merges, a new deployment to staging is triggered
- when all are happy the lead dev merges to master which triggers auto deployment to whatever instances are on tryout.host (the Editoria demo instance domain)
Any service provider can also make use of these triggers but we can discuss this on a case by case basis
The main thing the community needs to be aware of is that new features will be made available to be tested as each is completed. It is then up to the community to QA the release. If all is well it will be merged into the main Editoria code base.
Note: the same process will be followed for Wax (we should probably do the same also for xpub-collabra)