[OE-core] [PATCH 00/19] Recipe updates and version check fixes

[Alexander Kanavin]

On 10/20/2016 07:36 PM, akuster808 wrote:
> The issue is not updating master. It is about following the process.
> http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
>
>  Many of the changes don't comply to:
>
> "Commit with a concise and descriptive message - one that explains
> your changes in a way others get a short overview without looking at
> the code."

Key words are "your changes". When a recipe is updated to a newer
version, the commit message typically includes:

1) what is the new version

2) what changes to the recipe have been done and why (changes to
configure flags, changes to patches applied, changes to licensing
information, any other changes).

Also describing changes done by the upstream is not required for
compliance with the process.

Here's the deal: when 90 percent of oe-core's nearly 800 recipes are
kept up to date by maybe seven people from two companies, on top of all
the other stuff to be fixed and looked at, there's simply no bandwidth
for more. We plan to distribute recipe maintenance and spread it to a
lot more people involved in oe-core, and maybe then commit messages will
have summaries of upstream work as a rule.

> This has nothing to do with the correct way a stable branch would
> update a package. It is about providing some information so
> maintainers can make a decision on what to do.

Before that, we would also need reporting tools that can distinguish 
between new major releases, and new point releases in stable series. If 
I update webkit to a new major release and include a link to 
http://blogs.igalia.com/carlosgc/2016/09/20/webkitgtk-2-14/ in the 
commit log, that's not a particularly useful information for you, 
because what you really need to know as a stable branch maintainer is 
whether there are new bugfix releases of webkit in a previous major 
version that your stable release contains.


Alex