From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Fri, 31 Aug 2018 11:49:38 -0400 Subject: [U-Boot] u-boot release and feature set In-Reply-To: References: <20180829015738.GZ26633@bill-the-cat> Message-ID: <20180831154938.GR26633@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: u-boot@lists.denx.de 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, > >=20 > >> -----Original Message----- > >> From: Tom Rini > >> Sent: Wednesday, August 29, 2018 7:28 AM > >> To: Prabhakar Kushwaha > >> 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.safeli= nks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.denx.de%2Fwiki%2FU-&= ;data=3D02%7C01%7Cyork.sun%40nxp.com%7C9b263f9701134c98b63208d60d5d1d5e%7C6= 86ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C636711090913158275&sdata=3DZJ= ZMJUnx1LUwWMrU5%2F3kbfDo8X0GK%2BfvIqJO%2BObB4aY%3D&reserved=3D0 > >> Boot/ReleaseCycle but not the feature set. > >>> May be I am looking at wrong place =E2=98=B9 > >> > >> 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 s= ome > >> useful information for a detailed changelog. > >> > > Feature set is good thing to have per release. It help us in taking dec= ision of upreving u-boot (now or later).=20 > >=20 > > A suggestion, can we ask feature set details in every pull request from= sub-maintainers.=20 > > Or > > A blog can also be maintained, where sub-maintainer can write feature s= et per pull request.=20 > >=20 > > Sub-maintainers have better idea what feature they are providing. =20 > > Feature set can also be published per sub-system (instead of pick and c= hoose). =20 >=20 > 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. --=20 Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: