[oe] [warrior][patch 02/34] python-pyasn1: upgrade 0.4.4 -> 0.4.5

[Adrian Bunk]

On Tue, May 21, 2019 at 07:52:49AM -0700, akuster808 wrote:
> 
> 
> On 5/20/19 11:40 PM, Adrian Bunk wrote:
> > On Mon, May 20, 2019 at 08:56:02PM -0700, Armin Kuster wrote:
> >> From: Zang Ruochen <zangrc.fnst at cn.fujitsu.com>
> >>
> >> -Upgrade from python-pyasn1_0.4.4.bb to python-pyasn1_0.4.5.bb.
> >>
> >> -Upgrade from python3-pyasn1_0.4.4.bb to python3-pyasn1_0.4.5.bb
> >>
> >> -License-Update: Copyright year updated to 2019.
> >>
> >> Signed-off-by: Zang Ruochen <zangrc.fnst at cn.fujitsu.com>
> >> Signed-off-by: Khem Raj <raj.khem at gmail.com>
> >> Signed-off-by: Armin Kuster <akuster808 at gmail.com>
> >> ..
> > No reason is provided why this should be upgraded in a stable branch.
> 
> There is no meta-openembedded process or requirements for stable
> branches  to provide reasons in commit messages.
> 
> The precedent in the community is to provide minimal or no comments in a
> commit message. So the burned is placed on the Stable branch maintainer
> to do the leg work the community as whole should have done.
>...

For master the default action should be to upgrade to the latest
version, and no further rationale is required for this.

For stable branches the default action should be to do nothing, unless
there is a reason why something needs backporting or fixing in stable.

Stable branch maintainance can anyways not be based on just 
cherry-picking commits from master. Many important fixes, especially 
many CVE fixes, will need a different fix in a stable branch than in 
master.

> - armin

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed