U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] u-boot release and feature set
Date: Fri, 31 Aug 2018 11:49:38 -0400	[thread overview]
Message-ID: <20180831154938.GR26633@bill-the-cat> (raw)
In-Reply-To: <DB7PR04MB4298F30FE2176A1B84400F4A9A0F0@DB7PR04MB4298.eurprd04.prod.outlook.com>

On Fri, Aug 31, 2018 at 03:46:29PM +0000, York Sun wrote:
> On 08/28/2018 08:11 PM, Prabhakar Kushwaha wrote:
> > Thanks Tom for responding,
> > 
> >> -----Original Message-----
> >> From: Tom Rini <trini@konsulko.com>
> >> Sent: Wednesday, August 29, 2018 7:28 AM
> >> To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
> >> Cc: u-boot at lists.denx.de
> >> Subject: Re: [U-Boot] u-boot release and feature set
> >>
> >> On Tue, Aug 28, 2018 at 06:48:13AM +0000, Prabhakar Kushwaha wrote:
> >>
> >>> Hi Tom,
> >>>
> >>> Every u-boot release announcement has a very high level feature set.
> >>> I am wondering, if you also maintain detailed feature list  per u-boot
> >> release?
> >>>
> >>> I can see "Statistics" details per release from https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.denx.de%2Fwiki%2FU-&amp;data=02%7C01%7Cyork.sun%40nxp.com%7C9b263f9701134c98b63208d60d5d1d5e%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636711090913158275&amp;sdata=ZJZMJUnx1LUwWMrU5%2F3kbfDo8X0GK%2BfvIqJO%2BObB4aY%3D&amp;reserved=0
> >> Boot/ReleaseCycle but not the feature set.
> >>> May be I am looking at wrong place ☹
> >>
> >> It's been asked from time to time but I am simply bad about it.  I had tried
> >> parsing the git logs every -rc to come up with something more detailed, but
> >> that didn't last.  If more people did signed tags that would provide some
> >> useful information for a detailed changelog.
> >>
> > Feature set is good thing to have per release. It help us in taking decision of upreving u-boot (now or later). 
> > 
> > A suggestion, can we ask feature set details in every pull request from sub-maintainers. 
> > Or
> > A blog can also be maintained, where sub-maintainer can write feature set per pull request. 
> > 
> > Sub-maintainers have better idea what feature they are providing.  
> > Feature set can also be published per sub-system (instead of pick and choose).  
> 
> I think a short description in pull request can work. Parsing git log
> doesn't have the weight on each commit. We don't need to know every
> details of a platform fix, we care more on wider and bigger changes.

I really would appreciate the level of detail Linus' tree gets in signed
commit messages being in the U-Boot tree too.  No, it's not perfect and
it does need someone to make it more digestible, but it's a good
starting point.  And the people that do send me signed tags do a good
job too I think.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180831/6eafa299/attachment.sig>

  reply	other threads:[~2018-08-31 15:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28  6:48 [U-Boot] u-boot release and feature set Prabhakar Kushwaha
2018-08-29  1:57 ` Tom Rini
2018-08-29  3:11   ` Prabhakar Kushwaha
2018-08-31 15:46     ` York Sun
2018-08-31 15:49       ` Tom Rini [this message]
2018-08-31 15:59         ` York Sun
2018-08-31 16:30           ` Tom Rini
2018-08-31 16:45             ` York Sun
2018-08-31 16:58               ` Tom Rini

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=20180831154938.GR26633@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.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