From: Joel Stanley <joel@jms.id.au>
To: Alexander Amelkin <a.amelkin@yadro.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Brad Bishop <bradleyb@fuzziesquirrel.com>
Subject: Re: Proposals for commit log policy
Date: Thu, 23 Aug 2018 09:28:03 +0930 [thread overview]
Message-ID: <CACPK8XdtitrjvDpuiPiz_ew03m972ueGRXAhd4kM_z6YSVtL3A@mail.gmail.com> (raw)
In-Reply-To: <0ef9181f-eb70-552b-3411-da2bc9676be1@yadro.com>
On Tue, 21 Aug 2018 at 22:01, Alexander Amelkin <a.amelkin@yadro.com> wrote:
> =================
> some-package: bump version 62286ef3 to 4fa63380
>
> Author Name (2):
> commit 1 synopsis
> another commit synopsis
>
> Another Author (3):
> great commit
> yet another great commit
> fix previous not-so-great commit
>
> Change-Id: some-long-gerrit-hash
> Signed-off-by: The Version Bumper <bumper@nowhere.net>
> =================
> What do you think? Is this feasible? Any other ideas how we could simplify creating release notes suitable for end users?
I think this is a great suggestion. I would also like to see this happen.
Having the maintainers or authors of the packages submit their bumps
would ensure this does not become a burden for the central repository
maintainer.
An advantage of the maintainers of individual packages submitting
their changes is they know the best timing for integrating their
changes, and know what relevant details should be added to the bump
commit message.
Cheers,
Joel
next prev parent reply other threads:[~2018-08-22 23:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 12:29 Proposals for commit log policy Alexander Amelkin
2018-08-22 15:01 ` Gunnar Mills
2018-08-23 8:23 ` Alexander Amelkin
2018-08-22 20:39 ` Tanous, Ed
2018-08-23 8:44 ` Alexander Amelkin
2018-08-28 22:40 ` Tanous, Ed
2018-08-22 23:58 ` Joel Stanley [this message]
2018-08-28 10:29 ` Brad Bishop
2018-08-28 15:43 ` Andrew Geissler
2018-08-28 16:13 ` Patrick Venture
2018-08-28 17:44 ` Gunnar Mills
2018-08-28 22:20 ` Tanous, Ed
2018-08-28 22:43 ` Kun Yi
2018-09-04 20:20 ` Brad Bishop
2018-09-04 23:38 ` Patrick Venture
2018-09-06 13:13 ` Alexander Amelkin
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=CACPK8XdtitrjvDpuiPiz_ew03m972ueGRXAhd4kM_z6YSVtL3A@mail.gmail.com \
--to=joel@jms.id.au \
--cc=a.amelkin@yadro.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.