summaryrefslogtreecommitdiff
path: root/doc/dev/Release.md
Commit message (Collapse)AuthorAgeFilesLines
...
* changelog style: promote tersenessNick Mathewson2025-01-281-1/+2
|
* changelog style: allow bare-noun style sometimes.Nick Mathewson2025-01-281-3/+10
|
* changelog style: text from @diziet about audienceNick Mathewson2025-01-281-0/+8
|
* changelog style: text from @arma.Nick Mathewson2025-01-281-1/+16
|
* Changelog template: typo fix from @gabi-250.Nick Mathewson2025-01-281-1/+1
|
* Release.md: Suggestions from Diziet about style guideNick Mathewson2025-01-281-5/+12
|
* Write a styleguide for our CHANGELOG.md.Nick Mathewson2025-01-281-1/+203
| | | | | | | | This is based in part on the C Tor changelog standards, in part on an old hacking styleguide I found, and in part on past changelogs. It also includes a template to help start a new changelog.
* Merge branch 'release_clarify_pages' into 'main'Nick Mathewson2024-12-041-4/+27
|\ | | | | | | | | Release.md: clarify some post-release steps See merge request tpo/core/arti!2614
| * release: Clarify how to alert network-team and when.Nick Mathewson2024-11-121-1/+10
| |
| * Release.md: Add an "unfreeze the tree" stepNick Mathewson2024-11-051-1/+4
| |
| * Release.md: Add "email bekeela" step, with explanation.Nick Mathewson2024-11-051-1/+7
| |
| * Clarify "update pages branch" in the Release.md instructions.Nick Mathewson2024-11-051-2/+7
| |
* | maint: Add exclusion feature to `fixup-features`Clara Engler2024-12-031-1/+1
|/ | | | | | | | This commit adds an `--exclude <PREFIX>` argument to the `fixup-features` tool in order to ignore crate paths for crates that we do not publish, mainly those in the `examples/` and `maint/` directory. Fixes #1766
* maint/tag-arti-releaes: New scriptIan Jackson2024-06-271-4/+2
|
* Release.md: Say to run maint/update-md-linksIan Jackson2024-06-271-9/+7
| | | | Not the raw gen_md_links utility.
* maint/changelog-syntax-fiddle: New scriptIan Jackson2024-06-271-0/+3
|
* Update Release.md to reference new ownership scriptIan Jackson2024-06-241-1/+1
|
* Release.md: Mention check-crate-owners.Nick Mathewson2024-06-101-0/+4
|
* Rename list_crates_publish to list_cratesIan Jackson2024-05-081-2/+2
|
* Release.md: Provide commands for bench lockfilesIan Jackson2024-05-071-1/+6
| | | | | As per https://gitlab.torproject.org/tpo/core/arti/-/merge_requests/2118#note_3025016
* Release.md: clarify wording re hashx and equixNick Mathewson2024-05-071-1/+1
|
* Release.md: Say to use list_crates_publishIan Jackson2024-05-071-2/+2
|
* Release.md: say to use maint/cargo-publishIan Jackson2024-05-071-8/+6
|
* Release.md: Document the need to update the extra Cargo.lockIan Jackson2024-05-071-0/+5
|
* Release.md: Clarify structure slightlyIan Jackson2024-03-261-6/+6
|
* Release.md: Correct set-version rubricsIan Jackson2024-03-251-1/+3
|
* doc/Release.md: Initial cut of changes apropos new semver approachIan Jackson2024-03-251-1/+30
|
* doc/Release.md: Move a comment about committing lockfilesIan Jackson2024-03-251-3/+2
|
* Release.md: Document a simpler way of getting the crates with no changes.Gabriela Moldovan2024-03-051-2/+4
|
* Release.md: Add usage example for semver-checks.Gabriela Moldovan2024-03-051-1/+1
|
* Release.md: Add usage example for fixup-features.Gabriela Moldovan2024-03-051-0/+6
|
* Release.md: Suggest git log --topo-orderIan Jackson2024-02-061-1/+1
| | | | This causes commits to be reliably grouped by the MR they're in.
* doc/Release.md: Discuss trouble with publicationIan Jackson2024-02-051-0/+4
|
* Introduce maint/list_crates_publishIan Jackson2024-02-051-1/+1
|
* doc/Release.md: Discuss maint/gen_md_links a bit moreIan Jackson2024-02-051-0/+5
|
* Update changed_crates and Release.md to robustify release processNick Mathewson2023-10-041-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 cratesNick Mathewson2023-08-011-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 typosDimitris Apostolou2023-07-221-3/+3
|
* Release.md: Add an extra semver-checks to the process.Nick Mathewson2023-06-301-0/+3
| | | | (We didn't do this previously, but it is a good idea.)
* Release.md: Revise the release sectionsNick Mathewson2023-06-301-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 sectionsNick Mathewson2023-06-301-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 Mathewson2023-06-301-0/+18
|
* Release.md: Write the "are we ready to release" section.Nick Mathewson2023-06-301-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 Mathewson2023-06-301-1/+10
|
* doc/dev/Release.md: patch release workflowIan Jackson2023-04-041-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 processNick Mathewson2022-12-101-0/+2
|
* Move developer-facing documentation into a doc/dev subdirNick Mathewson2022-12-051-0/+57
Closes #576.
generated by cgit v1.2.3 (git 2.46.0) at 2026-08-26 21:36:07 +0000