# Prerelease branches for eportal and kcarectl I propose two branches `kc-next` and `eportal-next` to merge reviewed/verified patches to accumulate changes going into next release. It will allow: * to solve current possible instability of `master` branch and; * to release hot fixes without testing all ready-patches stack; * to see actual list of tasks going to be released `git diff master..kc-next`; ## Dev process The only thing changed for developers is `git review` invocation. To publish patch one have to call: ``` git review kc-next ``` or ``` git review eportal-next ``` ## Release master process Release master should merge `kc-next` and `eportal-next` with `master` branch before release to incorporate changes from non-python kernelcare members.