Branch Maintenance process clarification

Branch Maintenance process clarification

[akuster808]

Hello,

I am reviewing the stable branch maintenance for Yocto and would like
some clarification on a few steps.
https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance

6. Split out any bitbake changes and send them to the bitbake-devel
mailing list (marking them with the appropriate stable version in the
subject line e.g. [1.20])

AK] I have not seen this being done in the past. Should we start doing
this or update the process ?

7. Split out OE-Core changes and create an openembedded-core-contrib
branch containing them; send the cover letter only (marking it as such
in the subject) to the openembedded-core mailing list.

AK] I don't have write access to do this, so this will be a problem.

8. Split out any meta-yocto changes and create a poky-contrib branch
containing them; send the cover letter only (marking it as such in the
subject) to the poky mailing list.

AK] Is this required?

I do agree that the downstream repos are where the changes should be
pushed first  then feed poky. This is not what I have seen happen in the
past nor did I do it for dizzy either.

regards,
Armin

Re: [yocto] Branch Maintenance process clarification

[Khem Raj]

On Sun, May 15, 2016 at 11:11 AM, akuster808 <akuster808@gmail.com> wrote:
> Hello,
>
> I am reviewing the stable branch maintenance for Yocto and would like
> some clarification on a few steps.
> https://wiki.yoctoproject.org/wiki/Stable_branch_maintenance
>
> 6. Split out any bitbake changes and send them to the bitbake-devel
> mailing list (marking them with the appropriate stable version in the
> subject line e.g. [1.20])
>
> AK] I have not seen this being done in the past. Should we start doing
> this or update the process ?

I would also suggest to add OE-Core branchname along with bitbake version
[1.20][krogoth] or [krogoth/1.20] some thing like that

>
> 7. Split out OE-Core changes and create an openembedded-core-contrib
> branch containing them; send the cover letter only (marking it as such
> in the subject) to the openembedded-core mailing list.
>
> AK] I don't have write access to do this, so this will be a problem.

Ask Michael to add your keys to contrib repo.

>
> 8. Split out any meta-yocto changes and create a poky-contrib branch
> containing them; send the cover letter only (marking it as such in the
> subject) to the poky mailing list.
>
> AK] Is this required?

yes.

>
> I do agree that the downstream repos are where the changes should be
> pushed first  then feed poky. This is not what I have seen happen in the
> past nor did I do it for dizzy either.

Usually changes flow into upstream layers and then get merged into
downstream distros
like poky and others.

>
> regards,
> Armin
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto