Support and maintenance
Last updated
My repositories are personal projects that I publish because they may be useful to someone else. This page says what you can and cannot expect.
Best effort, no SLA
I answer issues and pull requests when I can. There is no response-time guarantee, no commercial support and no promise that a feature request will be accepted. If you depend on a project, pin a version and be ready to fork.
What is supported
- The latest release, or the default branch where a repository has no releases.
- Older versions are not patched. Upgrade first, then report the problem again if it persists.
- Security fixes follow the security policy.
Reporting a bug
Open an issue in the repository with the version or commit, what you did, what you expected and what happened. A minimal reproduction is worth more than a long description. Changes you want to make yourself: see contributing.
Status of a repository
- Active: developed and answered regularly.
- Maintenance: fixes and security updates only.
- Archived: read-only on GitHub, not maintained, no fixes of any kind. You may fork it under its licence.
The status is stated in the repository's README when it is not Active.
Deprecation notice
When I plan to remove a feature or retire a project I announce it in the README and the release notes at least 30 days before the change where that is possible, and name the replacement if there is one.
rclone-colab
rclone-colab is a single-user application for my own account. It is not offered to anyone else and has no support.