| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | maint/tag-arti-releaes: New script | Ian Jackson | 2024-06-27 | 1 | -4/+2 |
| | | |||||
| * | Release.md: Say to run maint/update-md-links | Ian Jackson | 2024-06-27 | 1 | -9/+7 |
| | | | | | Not the raw gen_md_links utility. | ||||
| * | maint/changelog-syntax-fiddle: New script | Ian Jackson | 2024-06-27 | 1 | -0/+3 |
| | | |||||
| * | Update Release.md to reference new ownership script | Ian Jackson | 2024-06-24 | 1 | -1/+1 |
| | | |||||
| * | Release.md: Mention check-crate-owners. | Nick Mathewson | 2024-06-10 | 1 | -0/+4 |
| | | |||||
| * | Rename list_crates_publish to list_crates | Ian Jackson | 2024-05-08 | 1 | -2/+2 |
| | | |||||
| * | Release.md: Provide commands for bench lockfiles | Ian Jackson | 2024-05-07 | 1 | -1/+6 |
| | | | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2118#note_3025016 | ||||
| * | Release.md: clarify wording re hashx and equix | Nick Mathewson | 2024-05-07 | 1 | -1/+1 |
| | | |||||
| * | Release.md: Say to use list_crates_publish | Ian Jackson | 2024-05-07 | 1 | -2/+2 |
| | | |||||
| * | Release.md: say to use maint/cargo-publish | Ian Jackson | 2024-05-07 | 1 | -8/+6 |
| | | |||||
| * | Release.md: Document the need to update the extra Cargo.lock | Ian Jackson | 2024-05-07 | 1 | -0/+5 |
| | | |||||
| * | Release.md: Clarify structure slightly | Ian Jackson | 2024-03-26 | 1 | -6/+6 |
| | | |||||
| * | Release.md: Correct set-version rubrics | Ian Jackson | 2024-03-25 | 1 | -1/+3 |
| | | |||||
| * | doc/Release.md: Initial cut of changes apropos new semver approach | Ian Jackson | 2024-03-25 | 1 | -1/+30 |
| | | |||||
| * | doc/Release.md: Move a comment about committing lockfiles | Ian Jackson | 2024-03-25 | 1 | -3/+2 |
| | | |||||
| * | Release.md: Document a simpler way of getting the crates with no changes. | Gabriela Moldovan | 2024-03-05 | 1 | -2/+4 |
| | | |||||
| * | Release.md: Add usage example for semver-checks. | Gabriela Moldovan | 2024-03-05 | 1 | -1/+1 |
| | | |||||
| * | Release.md: Add usage example for fixup-features. | Gabriela Moldovan | 2024-03-05 | 1 | -0/+6 |
| | | |||||
| * | Release.md: Suggest git log --topo-order | Ian Jackson | 2024-02-06 | 1 | -1/+1 |
| | | | | | This causes commits to be reliably grouped by the MR they're in. | ||||
| * | doc/Release.md: Discuss trouble with publication | Ian Jackson | 2024-02-05 | 1 | -0/+4 |
| | | |||||
| * | Introduce maint/list_crates_publish | Ian Jackson | 2024-02-05 | 1 | -1/+1 |
| | | |||||
| * | doc/Release.md: Discuss maint/gen_md_links a bit more | Ian Jackson | 2024-02-05 | 1 | -0/+5 |
| | | |||||
| * | Update changed_crates and Release.md to robustify release process | Nick Mathewson | 2023-10-04 | 1 | -0/+7 |
| | | | | | | | | | | | In particular, this change should help avoid the kind of problem we ran into as #1054 and fixed with 00e4405943498754, where a crate changed only in which versions of our crates it depended upon, and we didn't notice that we had to update its version too. This commit also fixes a couple of minor issues in the `changed_crates` script, and gives it a verbose mode. | ||||
| * | Script to bump patchlevel without touching other crates | Nick Mathewson | 2023-08-01 | 1 | -4/+2 |
| | | | | | | | | | Closes #945. Based on @diziet's comment in #945, with a little extra safety and paranoia. We use this for cases when there are trivial changes only in one of our crates. | ||||
| * | Fix typos | Dimitris Apostolou | 2023-07-22 | 1 | -3/+3 |
| | | |||||
| * | Release.md: Add an extra semver-checks to the process. | Nick Mathewson | 2023-06-30 | 1 | -0/+3 |
| | | | | | (We didn't do this previously, but it is a good idea.) | ||||
| * | Release.md: Revise the release sections | Nick Mathewson | 2023-06-30 | 1 | -32/+21 |
| | | | | | | | | | * Remove instructions to sleep * Explain how to tag * Remind myself about the workaround for Fedora's delightful gpg/yubikey configuration. * Note that we should update "pages" till the blog post is up. | ||||
| * | Release.md: document preparation sections | Nick Mathewson | 2023-06-30 | 1 | -13/+120 |
| | | | | | | | | | | | | | | I've split this into "what I do in the days leading up to the release" and "what I do right before the release". There's a lot more detail now, including: * up-to-date invocations for `cargo upgrade` * up-to-date changelog instructions * our current version-bumping instructions * possible side-effects from version bumps. | ||||
| * | Release.md: Write a tools section. | Nick Mathewson | 2023-06-30 | 1 | -0/+18 |
| | | |||||
| * | Release.md: Write the "are we ready to release" section. | Nick Mathewson | 2023-06-30 | 1 | -3/+37 |
| | | | | | | | | | | | | | * Remove references to a couple of things that our CI now does for us (`cargo_audit` and `check_licenses`). * Mention ~Blocker issues and MRs. * Mention that some of our CI steps are allowed-to-fail, but failures should be examined. * Mention that some of our tools have exception lists that should get reviewed. * Mention `semver-checks` and `fixup-features`. | ||||
| * | Release.md: Add subheadings for "how to release." | Nick Mathewson | 2023-06-30 | 1 | -1/+10 |
| | | |||||
| * | doc/dev/Release.md: patch release workflow | Ian Jackson | 2023-04-04 | 1 | -0/+87 |
| | | | | | | | | | | We did roughly this today. We put the CHANGELOG.md change in its own MR, so it didn't end up in the tor-llcrypto-v0.4.4 tag. It would have been better to do it the other way so that's what I've documented. I couldn't test-format this with pandoc because it got tricked by some of the `$` into trying to run TeX. | ||||
| * | Add another step to the release process | Nick Mathewson | 2022-12-10 | 1 | -0/+2 |
| | | |||||
| * | Move developer-facing documentation into a doc/dev subdir | Nick Mathewson | 2022-12-05 | 1 | -0/+57 |
| Closes #576. | |||||
