Reliability Kit is owned and maintained by the Customer Products Reliability team at the Financial Times.
It's been designed to make other Customer Products systems easier to support in production environments.
However, we hope that it will be useful to other teams at the FT.
We follow Semantic Versioning 2.0.0.
This means that we will not make breaking changes to Reliability Kit without a corresponding major
release (like moving from v1.0.0 to v2.0.0). These changes will be documented in a way that helps
users migrate. We will consider the scale of these migrations and try to minimise the impact on the
teams using this library and, where possible, we will mark features as deprecated some time ahead
of a major release.
The Reliability team is always available to work with teams in Customer Products. Our priority is making sure that FT.com, our iOS and Android apps and our Data Journalism work are available to our subscribers.
Please contact us in #cp-reliability on Slack with any bug reports, feature ideas or requests for help.
If you're experiencing an issue in production, message #ft-next-support and tag @cp_reliability so that we see it immediately.
Where time allows, we would love to improve Reliability Kit so that it better meets the needs of other users at the FT. This could include:
- reviewing minor code changes that will make these packages work better for you (please read the contributing guide before opening pull requests)
- meeting with you to discuss features that you would like to add
- pairing with you on implementing larger features
Please create an issue on this repo and we'll be in touch with you to discuss your needs.
We aim to give pull requests on Reliability Kit a first review within 3 working days.
Unfortunately we're unable to offer any guarantees of support to users outside the FT.