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

[akuster808]

On 10/20/2016 02:16 AM, Alexander Kanavin wrote:
> On 10/19/2016 10:42 PM, akuster808 wrote:
>> Are these updates just bug fixes or do they also contain new features /
>> enhancements. Having a little more description in the commit will help
>> the morty maintainer determine if any of the updates are suitable to
>> backporting.
>
> They're both. The updates in master happen not because of specific 
> features or bugfixes, but simply because we want to stay as close to 
> upstream as possible at all times, because there is less pain in many 
> incremental updates as opposed to single massive updates that jump 
> over a lot of code changes.
>
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."


> If stable releases want to do recipe version updates, the correct way 
> to do that is to have automatic regression testing on every level, 
> from oe-core all the way to the product image. Manually analyzing git 
> log output and summarizing release announcements or whatnot for all of 
> oe-core packages is labour-intensive and error/omission prone for 
> everyone involved.

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.

- armin
>
> Alex
>