From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>, dwz@sourceware.org
Subject: Re: [PUSHED] Update FSF Copyright years to include 2021.
Date: Thu, 18 Feb 2021 14:45:39 +0100 [thread overview]
Message-ID: <a9d96956-4fab-4408-de3c-3b4ddd35cc43@suse.de> (raw)
In-Reply-To: <54beb0a7ae1bb32cbd6b44fa9543ed4c91316891.camel@klomp.org>
On 2/18/21 2:39 PM, Mark Wielaard wrote:
> Hi Tom,
>
> On Sun, 2021-02-14 at 08:58 +0100, Tom de Vries wrote:
>> On 2/12/21 1:29 PM, Mark Wielaard wrote:
>>> This should have been done as part of commit f7c0d8afb
>>> "Sync dwarf2.{def,h} and dwarfnames.c from gcc/libiberty."
>>
>> FWIW, there's a script contrib/release/gen-copyright-years.sh, that
>> comes to the same conclusion:
>> ...
>
> O nice, I wasn't aware of the contrib/release scripts.
> So we have everything needed to do a release there?
Well, I don't know if it's everything, but I've tried to write scripts
to automate the process.
There's:
...
$ ls -1 contrib/release/*.sh
contrib/release/do-release.sh
contrib/release/gen-copyright-years.sh
contrib/release/upload-release.sh
...
So:
- gen-copyright-years updates COPYRIGHT_YEARS.
- do-release does a git tag and updates VERSION
- upload-release.sh uploads the release to the sourceware site
I guess other things to do are:
- sent out release announcement, and
- update webpage.
Thanks,
- Tom
prev parent reply other threads:[~2021-02-18 13:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 12:29 Mark Wielaard
2021-02-14 7:58 ` Tom de Vries
2021-02-18 13:39 ` Mark Wielaard
2021-02-18 13:45 ` Tom de Vries [this message]
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=a9d96956-4fab-4408-de3c-3b4ddd35cc43@suse.de \
--to=tdevries@suse.de \
--cc=dwz@sourceware.org \
--cc=mark@klomp.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).