From 0d29e1b8de605be202aea148e0b8398811b21df1 Mon Sep 17 00:00:00 2001 From: Colomban Wendling Date: Sun, 13 Nov 2016 19:06:55 +0100 Subject: [PATCH] Update making-a-release to mention new scripts --- doc/making-a-release | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/doc/making-a-release b/doc/making-a-release index 5b5123e9..b6a1db1d 100644 --- a/doc/making-a-release +++ b/doc/making-a-release @@ -9,7 +9,7 @@ to filter commits by a particular developer name. Ensure version numbers are all updated in: configure.ac geany_private.rc geany.exe.manifest doc/geany.txt -Ensure release date is updated in: +Ensure release date is updated in (use scripts/set-release-date if not): NEWS doc/geany.txt doc/geany.1.in Check GEANY_CODENAME is set in src/geany.h. @@ -40,12 +40,13 @@ current/hacking.html. Announce on geany, devel, i18n mailing lists (check you're subscribed). Put a news item on SourceForge (https://sourceforge.net/p/geany/news/) -and a new release on GitHub (https://github.com/geany/geany/releases). +and a new release on GitHub (https://github.com/geany/geany/releases -- +use scripts/github-news to generate the contents). Update the topic on the IRC channel (/msg chanserv op #geany). For non-master releases, merge NEWS into master and any branch-only commits that need to merged. -For merge releases, bump version strings and codename and merge unstable -branch if any. +For merge releases, bump version strings and codename (use scripts/version-bump) +and merge unstable branch if any.