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@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....
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.
York