22
33## Setup Your Development Environment
44
5- If you want to contribute code to ` xrpl-rust ` , the following sections describe
5+ If you want to contribute code to ` xrpl-rust ` , the following sections describe
66how to set up your developer environment.
77
88### Setup the Rust/Cargo Environment
99
10- Getting started with Rust and ` xrpl-rust ` is easy. To install ` rust ` and
10+ Getting started with Rust and ` xrpl-rust ` is easy. To install ` rust ` and
1111` cargo ` follow these steps:
1212
13- * Install [ ` rust ` ] ( https://doc.rust-lang.org/cargo/getting-started/installation.html ) :
13+ - Install [ ` rust ` ] ( https://doc.rust-lang.org/cargo/getting-started/installation.html ) :
1414
1515 curl https://sh.rustup.rs -sSf | sh
1616
17- * Update rust using ` rustup ` and install a few development dependencies:
17+ - Update rust using ` rustup ` and install a few development dependencies:
1818
1919 // Rustup
2020 rustup update
@@ -26,11 +26,11 @@ Getting started with Rust and `xrpl-rust` is easy. To install `rust` and
2626
2727### Git ` pre-commit ` Hooks
2828
29- To run linting and other checks, ` xrpl-rust ` uses
29+ To run linting and other checks, ` xrpl-rust ` uses
3030[ ` pre-commit ` ] ( https://pre-commit.com/ ) .
3131
32- > This should already be setup thanks to
33- [ ` cargo-husky ` ] ( https://github.com/rhysd/cargo-husky )
32+ > This should already be setup thanks to
33+ > [ ` cargo-husky ` ] ( https://github.com/rhysd/cargo-husky )
3434
3535### Run the Formatter
3636
@@ -67,8 +67,8 @@ cargo test --all-features
6767
6868### Generate Documentation
6969
70- You can see the complete reference documentation at
71- [ ` xrpl-rust ` docs] ( https://docs.rs/xrpl ) .
70+ You can see the complete reference documentation at
71+ [ ` xrpl-rust ` docs] ( https://docs.rs/xrpl ) .
7272
7373You can also generate them locally using ` cargo ` :
7474
@@ -87,7 +87,7 @@ cargo audit
8787### Submitting Bugs
8888
8989Bug reports are welcome. Please create an issue using the default issue
90- template. Fill in * all * information including a minimal reproducible
90+ template. Fill in _ all _ information including a minimal reproducible
9191code example. Every function in the library comes with such an example
9292and can adapted to look like the following for an issue report:
9393
@@ -115,19 +115,28 @@ match derive_keypair(seed, validator) {
115115 },
116116};
117117```
118+
118119> This format makes it easy for maintainers to replicate and test against.
119120
120121## Release Process
121122
123+ 1 . Create a processing branch ` process/[VERSION] `
124+ 2 . Brach management:
125+ - If this is a new version, increment the version in the ` Cargo.toml ` and target ` main ` .
126+ - If this a patch release, chery-pick commits being released and target ` versions/v[major] ` .
127+ 3 . Collect required merge approvals.
128+ 4 . Merge release PR.
129+ 5 . [ TODO automate] Run ` cargo publish ` .
130+
122131### Editing the Code
123132
124- * Your changes should have unit and/or integration tests.
125- * New functionality should include a minimal reproducible sample.
126- * Your changes should pass the linter.
127- * Your code should pass all the actions on GitHub.
128- * Open a PR against ` main ` and ensure that all CI passes.
129- * Get a full code review from one of the maintainers.
130- * Merge your changes.
133+ - Your changes should have unit and/or integration tests.
134+ - New functionality should include a minimal reproducible sample.
135+ - Your changes should pass the linter.
136+ - Your code should pass all the actions on GitHub.
137+ - Open a PR against ` main ` and ensure that all CI passes.
138+ - Get a full code review from one of the maintainers.
139+ - Merge your changes.
131140
132141### Release
133142
0 commit comments