public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Duncan Mak <duncanmak@gmail.com>,
	kawa mailing list <kawa@sourceware.org>
Subject: Re: Time for a new release? 3.1.2?
Date: Wed, 28 Sep 2022 21:38:04 -0700	[thread overview]
Message-ID: <0aee6f41-9f36-e9ef-6761-e8d81a3b5f5f@bothner.com> (raw)
In-Reply-To: <CABgWrqpX6g_iRPj0MOeX6cO4s0j_J6LEiHtedd2WDJwonkimcg@mail.gmail.com>



On 9/28/22 10:53, Duncan Mak via Kawa wrote:
> Hello Per,
> 
> It's been over two years since the last release (3.1.1, 2020-01-16), I
> count 72 commits made to the master branch since then.
> 
> Would it be a good time to make a 3.1.2 release soon?

Might as well call it 3.2.

It would be helpful if someone went through the changes
(using 'git log' and **/ChangeLog) to summarize what has
change in a format suitable for doc/news.texi.

Also make a note of where the manual needs to be updated.

Minor tweaks and bug fixes don't need to be mentioned.

-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2022-09-29  4:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-28 17:53 Duncan Mak
2022-09-29  4:38 ` Per Bothner [this message]
2022-09-29 15:18   ` Arvydas Silanskas
2022-10-03 11:36     ` Arvydas Silanskas
2022-10-21  9:01       ` Arvydas Silanskas
2022-10-27  4:50         ` Shawn Wagner
2022-12-06  9:07           ` Arvydas Silanskas
2023-01-05 21:34             ` Per Bothner
2023-01-05 22:02               ` Damien Mattei
2023-01-06 12:16               ` Lassi Kortela
2023-01-08 18:11               ` Sascha Ziemann
2023-01-09  9:03                 ` Lassi Kortela
2023-01-09  9:42                   ` Arvydas Silanskas
2023-01-09 10:51                     ` Lassi Kortela

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0aee6f41-9f36-e9ef-6761-e8d81a3b5f5f@bothner.com \
    --to=per@bothner.com \
    --cc=duncanmak@gmail.com \
    --cc=kawa@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).