<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/arti.git/doc/dev/Release.md, branch arti-v1.2.0</title>
<subtitle>mirror of https://gitlab.torproject.org/tpo/core/arti
</subtitle>
<id>http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.0</id>
<link rel='self' href='http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.2.0'/>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/'/>
<updated>2024-02-06T14:00:41Z</updated>
<entry>
<title>Release.md: Suggest git log --topo-order</title>
<updated>2024-02-06T14:00:41Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-02-01T17:28:56Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=f2cb461098831ba252475b9829814de9f15135bc'/>
<id>urn:sha1:f2cb461098831ba252475b9829814de9f15135bc</id>
<content type='text'>
This causes commits to be reliably grouped by the MR they're in.
</content>
</entry>
<entry>
<title>doc/Release.md: Discuss trouble with publication</title>
<updated>2024-02-05T19:01:36Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-02-05T18:46:30Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=329b015d1362017d598258bb77f6d7ce27165e9b'/>
<id>urn:sha1:329b015d1362017d598258bb77f6d7ce27165e9b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Introduce maint/list_crates_publish</title>
<updated>2024-02-05T19:01:36Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-02-05T18:30:24Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b03e5d5e11c52faf441294c8c883a2dfbc0d2021'/>
<id>urn:sha1:b03e5d5e11c52faf441294c8c883a2dfbc0d2021</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc/Release.md: Discuss maint/gen_md_links a bit more</title>
<updated>2024-02-05T19:01:36Z</updated>
<author>
<name>Ian Jackson</name>
<email>ijackson@chiark.greenend.org.uk</email>
</author>
<published>2024-02-05T15:28:25Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=fb5ebe5ebde557dc4ec9387dd28243e5da8f463d'/>
<id>urn:sha1:fb5ebe5ebde557dc4ec9387dd28243e5da8f463d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Update changed_crates and Release.md to robustify release process</title>
<updated>2023-10-04T14:57:04Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-10-04T14:52:32Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=5de0e614fee34ecfeda761414a8600e6f5fb71dd'/>
<id>urn:sha1:5de0e614fee34ecfeda761414a8600e6f5fb71dd</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Script to bump patchlevel without touching other crates</title>
<updated>2023-08-01T16:57:58Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-08-01T16:57:58Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=b71b04eb849b693d17c74a82af62a63d9ac823e0'/>
<id>urn:sha1:b71b04eb849b693d17c74a82af62a63d9ac823e0</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>Fix typos</title>
<updated>2023-07-22T07:10:34Z</updated>
<author>
<name>Dimitris Apostolou</name>
<email>dimitris.apostolou@icloud.com</email>
</author>
<published>2023-07-22T07:10:34Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=947ddfff0cfac3fef0e3d7ebc14182c638a1d90b'/>
<id>urn:sha1:947ddfff0cfac3fef0e3d7ebc14182c638a1d90b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Release.md: Add an extra semver-checks to the process.</title>
<updated>2023-06-30T16:30:44Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-30T16:30:44Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=92daa577c203f97541989cee2fc8c6152fec0158'/>
<id>urn:sha1:92daa577c203f97541989cee2fc8c6152fec0158</id>
<content type='text'>
(We didn't do this previously, but it is a good idea.)
</content>
</entry>
<entry>
<title>Release.md: Revise the release sections</title>
<updated>2023-06-30T16:21:48Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-30T16:21:37Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=2f005a104758e69ef69230d2f521ed705eef665f'/>
<id>urn:sha1:2f005a104758e69ef69230d2f521ed705eef665f</id>
<content type='text'>
* 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.
</content>
</entry>
<entry>
<title>Release.md: document preparation sections</title>
<updated>2023-06-30T16:18:57Z</updated>
<author>
<name>Nick Mathewson</name>
<email>nickm@torproject.org</email>
</author>
<published>2023-06-30T16:18:57Z</published>
<link rel='alternate' type='text/html' href='http://git.dilluti0n.com/mirrors/arti.git/commit/?id=d0e00e4f4e362c40918a398af9e5d6df883a2d4a'/>
<id>urn:sha1:d0e00e4f4e362c40918a398af9e5d6df883a2d4a</id>
<content type='text'>
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.
</content>
</entry>
</feed>
