You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're responsible for keeping the Rust toolchain up to date, so we should have some rough guidelines and instructions.
I think we should aim to stay 2-3 versions within the latest release, with a 6-week release cycle that would have us updating roughly every 3-5 months (of course we can update faster if there's features we want or specific needs).
Not sure we need to specify the list of files to update since that could change (and hopefully we de-duplicate later on), but for completeness it's:
We're responsible for keeping the Rust toolchain up to date, so add some
rough guidelines and instructions.
The test plan is based off of
<freedomofpress/securedrop#6832>.
Fixes#79.
Describe the change
We're responsible for keeping the Rust toolchain up to date, so we should have some rough guidelines and instructions.
I think we should aim to stay 2-3 versions within the latest release, with a 6-week release cycle that would have us updating roughly every 3-5 months (of course we can update faster if there's features we want or specific needs).
Not sure we need to specify the list of files to update since that could change (and hopefully we de-duplicate later on), but for completeness it's:
(maybe we add some magic string like
RUST_VERSION
everywhere to make it easy to grep for)Test plan can be based off of freedomofpress/securedrop#6832
The text was updated successfully, but these errors were encountered: