From 022650dbffe04221d3d33f43570920be7a067523 Mon Sep 17 00:00:00 2001 From: "Dustin J. Mitchell" Date: Thu, 6 Mar 2025 07:43:41 -0500 Subject: [PATCH] Make updates after releasing (#3803) * add symlinks for ease of access * Update things after making a release, to maximize testing time --- CONTRIBUTING.md | 1 + RELEASING.md | 1 + doc/devel/contrib/releasing.md | 3 +++ 3 files changed, 5 insertions(+) create mode 120000 CONTRIBUTING.md create mode 120000 RELEASING.md diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 120000 index 000000000..a5e92ccc7 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1 @@ +doc/devel/contrib/development.md \ No newline at end of file diff --git a/RELEASING.md b/RELEASING.md new file mode 120000 index 000000000..51170bf7a --- /dev/null +++ b/RELEASING.md @@ -0,0 +1 @@ +doc/devel/contrib/releasing.md \ No newline at end of file diff --git a/doc/devel/contrib/releasing.md b/doc/devel/contrib/releasing.md index d8b4fa125..ffaf1ea67 100644 --- a/doc/devel/contrib/releasing.md +++ b/doc/devel/contrib/releasing.md @@ -24,3 +24,6 @@ To release Taskwarrior, follow this process: - Add a new item in `content/news` - Update `data/projects.json` with the latest version and a fake next version for "devel" - Update `data/releases.json` with the new version, and copy the tarball into `content/download`. +- Update various things, in a new PR: + - `cargo update` + - `git submodule update --remote --merge`