From: Jakub Jelinek <jakub@redhat.com>
To: Tom de Vries <tdevries@suse.de>
Cc: dwz@sourceware.org
Subject: Re: [PATCH] Add do-release.sh
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <20190729172036.GF15878@tucnak> (raw)
In-Reply-To: <20190722074131.GA32307@delia>
On Mon, Jul 22, 2019 at 09:41:33AM +0200, Tom de Vries wrote:
> Hi,
>
> this commit adds a script that:
> - bumps either the minor or the major version, using options
> --major or --minor
> - updates VERSION
> - commits VERSION update
> - tags VERSION update
>
> OK for trunk?
>
> Is there anything else involved in doing a release?
I think that is all, bumping VERSION, commiting and tagging was all I did in
the past.
One thing that might be worth doing is bump copyright years on files you've
modified, I know dwz.c has been using mostly Red Hat copyright, if you want
to use say FSF copyright, can you change that 2003 in there to 2003, 2019?
Or do you want to use SUSE copyright instead?
I guess because I have touched dwz.c last year the RH copyright should be
-2018 instead of -2015 too, and dwarf2.def should be probably changed to
1992-2018 FSF copyright, using the simple range. After the release we
should likely import new dwarf2.def and dwarf2.h from GCC tree.
Jakub
next prev parent reply other threads:[~2019-07-29 17:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Jakub Jelinek [this message]
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` [committed] Update --version copyright message Tom de Vries
2019-01-01 0:00 ` Branch creation: dwz-0.13-branch Tom de Vries
2019-01-01 0:00 ` [committed] Copy dwarf2.def, dwarf2.h and dwarfnames.c from gcc Tom de Vries
2019-01-01 0:00 ` [PATCH] Add do-release.sh Tom de Vries
2019-01-01 0:00 ` Michael Matz
2019-01-01 0:00 ` Jakub Jelinek
2019-01-01 0:00 ` Tom de Vries
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=20190729172036.GF15878@tucnak \
--to=jakub@redhat.com \
--cc=dwz@sourceware.org \
--cc=tdevries@suse.de \
/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).