From df077592279b39ddf4d66ea9955e3a039b2609d4 Mon Sep 17 00:00:00 2001 From: "B. Petersen" Date: Thu, 5 Dec 2024 19:49:21 +0100 Subject: [PATCH] update RELEASE.md --- RELEASE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index c2da6ce0b..871c936d7 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -21,7 +21,7 @@ the "update-core-and-stuff-DATE" PR can be merged without review then, create a "bump-to-VERSION" PR: 3. update CHANGELOG.md: - a) add title `## v1.2.3` or `## v1.2.3 Testflight` + a) add title `## v1.2.3` or `## v1.2.3 Testflight`, add date as `YYYY-MM` b) redact lines from `## Unreleased` there c) add core version to end of changelog entry as `- update to core 1.2.3` or `- using core 1.2.3` c) incorporate @@ -31,7 +31,7 @@ then, create a "bump-to-VERSION" PR: the entries should be summarized. this makes it easier for the end user to follow changes by showing major changes atop. -4. on major changes, add a device message to `ChatListController::viewDidLoad()` +4. on major changes, add a device message to `ChatListViewController::viewDidLoad()` or remove the old one. do not repeat the CHANGELOG here: write what really is the UX outcome in a few lines of easy speak without technical terms.