sapwood

Support Guidelines

Because Sapwood is currently a one-man project, I'm limited in the amount of support I can provide. Here are the guidelines:

Because Sapwood is currently a one-man project, I'm limited in the amount of support I can provide. Here are the guidelines:

Bugs & Issues

If you have an issue or have discovered a bug in the code, please create an issue on GitHub.

You may also fix the bug yourself and create a pull request.

Questions

If you have a question with anything related to Sapwood, please ask via a GitHub issue.

Doc Fixes

The documentation touches on many aspects and nuances of Sapwood, but there is certainly more to be done. And it's possible some of it is out of date. If you find something confusing and you need clarification, or if you find a bug or grammatical error, please create an issue on GitHub.

Version Support

taproot will (to the best of my ability) follow Semantic Versioning. Minor version releases will come frequently throughout v1.x.x, and they will be backward-compatible as much as possible. However, there will likely be a few items to clean up here and there to keep it rolling.

The general idea, however, is that you stay up to date with your current major version.

Using this logic, I will only fix bugs on the current minor version. In other words, you're expected to be up to date with your current major version.

It is yet to be determined the approach to supporting past major versions, as this will not be relevant for some time.