919888fe60
Add instructions on how to backport a feature to on older version of Scylla. It contains a detailed step-by-step instruction so that people unfamiliar with intricacies of Scylla's repository organization can easily get the hang of it. This is the guide I wish I had when I had to do my first backport. I put it in backport.md because that looks like the file responsible for this sort of information. For a moment I thought about `CONTRIBUTING.md`, but this is a really short file with general information, so it doesn't really fit there. Maybe in the future there will be some sort of unification (see #12126) Closes #12138 * github.com:scylladb/scylladb: dev/docs: add additional git pull to backport docs docs/dev: add a note about cherry-picking individual commits docs/dev: use 'is merged into' instead of 'becomes' docs/dev: mention that new backport instructions are for the contributor docs/dev: Add backport instructions for contributors
Scylla developer documentation
This folder contains developer-oriented documentation concerning the ScyllaDB codebase. We also have a wiki, which contains additional developer-oriented documentation. There is currently no clear definition of what goes where, so when looking for something be sure to check both.
Seastar documentation can be found here.
User documentation can be found on docs.scylladb.com
For information on how to build Scylla and how to contribute visit HACKING.md and CONTRIBUTING.md.