Commit 06c244a3 authored by Georges Racinet's avatar Georges Racinet 🦑
Browse files

README: rules for management of the default branch

these can be amended later, but it's occurring to me that
the interdependency with changes in Heptapod has to be
clarified, if only as a reference for myself.
parent 4625448d0965
......@@ -50,3 +50,17 @@ To test your local clone of heptapod/heptapod:
If you want to try changes to other components (e.g., `hg-git`), do something similar.
The paths can be seen in the Docker build logs, or you can read them in the [install script](https://dev.heptapod.net/heptapod/omnibus/blob/branch/heptapod/heptapod_docker/assets/install_heptapod.py)
## Adding new tests
### Branch and topics rules
The convention is that the tests in the default branch should pass against
the current `octobus/heptapod:latest` Docker image, so
* if you want to share a bug reproduction, please open a new topic
* even if a bug fix in heptapod has landed, please wait for Docker push to
publish the corresponding tests
* tests can be published before a Heptapod new release, but please have the
corresponding fixes landed and pushed to Docker Hub first.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment