For maintainers

Use this section when you are changing HQBase itself. Start with the job you need to do.

Contribute to HQBase Make a change, open the right pull requests, and hand it to an HQBase maintainer.

Change the documentation Choose the right page, keep one copy, and finish the documentation checks.

Make a product change Find the owning repository, protect customer data, and test the behavior.

Check a deployed change Run the staging checks without using production data or credentials.

Publish a release Package, sign, test, and publish an official HQBase release.

The usual order

1. Choose the repository or repositories that own the change.
2. Write down the product rule when behavior is changing.
3. Change the code and tests in every affected repository.
4. Update the reader documentation when people will install, use, or operate the product differently.
5. Run each repository’s full check and open linked pull requests.
6. An authorized HQBase maintainer uses official staging when the behavior crosses deployed systems.
7. An authorized maintainer publishes a signed release only after the exact candidate passes.

You are finished when the product, tests, and public documentation all describe the same behavior.