Danny stable release branch

Danny stable release branch

[Burton, Ross]

Hi,

Now that 1.3 is released[1] I can announce that I'm the Danny stable
release series maintainer.  This involves pulling any relevant
security fixes, build fixes and critical bug fixes from master, and
periodically rolling a 1.3.x release.

Obviously there's a lot of activity in master so whilst I intend to
consider every commit, if anyone submits patches to master that should
also be in danny, please say so either in a direct mail or with a tag
in the subject line.

Expect to see a ross/danny-next series in the poky-contrib repository
fairly soon where I'll be staging the commits.

Ross

[1] http://www.yoctoproject.org/blogs/davest/2012/yocto-project-v1.3-released
if anyone missed the news

Re: Danny stable release branch

[Marcin Juszkiewicz]

W dniu 26.10.2012 15:44, Burton, Ross pisze:
> Hi,
> 
> Now that 1.3 is released[1] I can announce that I'm the Danny stable
>  release series maintainer.  This involves pulling any relevant 
> security fixes, build fixes and critical bug fixes from master, and 
> periodically rolling a 1.3.x release.
> 
> Obviously there's a lot of activity in master so whilst I intend to 
> consider every commit, if anyone submits patches to master that 
> should also be in danny, please say so either in a direct mail or 
> with a tag in the subject line.

Are there chances that AArch64 related changes which are present in
master can get into danny? Everything other then gnu-config should be
safe and not affect other targets:

commit 468c074ba15cd4b93600d5ba5a1fdc032718d7c3
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date:   Thu Oct 4 16:15:08 2012 +0200

    pcmanfm: mark AArch64 as compatible

    Signed-off-by: Saul Wold <sgw@linux.intel.com>

commit c9514779de7fa6ea4cfa0c911cff25ea8c6a5152
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date:   Wed Oct 3 16:29:01 2012 +0200

    packagegroups: disable kexec, valgrind, lttng, systemtap on AArch64

    Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
    Signed-off-by: Saul Wold <sgw@linux.intel.com>

commit 1dbf17d221ee9d50c5de8c04144c92fdc78d6d73
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date:   Wed Oct 3 11:20:12 2012 +0200

    util-linux: add AArch64 support

    Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
    Signed-off-by: Saul Wold <sgw@linux.intel.com>

commit 490b12126aff7e8e59569ebb471ce04ba4962b7c
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date:   Wed Oct 3 11:18:33 2012 +0200

    openssl: add AArch64 support

    Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
    Signed-off-by: Saul Wold <sgw@linux.intel.com>

commit 39d71c8c41276091688decb64d418e1e3637e2b6
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date:   Thu Sep 27 15:13:08 2012 +0200

    insane.bbclass: add AArch64 support

    Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
    Signed-off-by: Saul Wold <sgw@linux.intel.com>

commit 9583a46221580ba46ebfd6d561d3a4d6b0d42eea
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date:   Thu Sep 27 14:59:25 2012 +0200

    kernel-arch.bblass: add AArch64 support

    Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
    Signed-off-by: Saul Wold <sgw@linux.intel.com>

commit fde788cf5b0e480a675d2aa256af0915a120bc65
Author: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Date:   Thu Sep 27 14:59:04 2012 +0200

    siteinfo.bbclass: add AArch64 support

    Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
    Signed-off-by: Saul Wold <sgw@linux.intel.com>

Re: Danny stable release branch

[Burton, Ross]

Hi Marcin,

On 26 October 2012 16:05, Marcin Juszkiewicz
<marcin.juszkiewicz@linaro.org> wrote:
> Are there chances that AArch64 related changes which are present in
> master can get into danny? Everything other then gnu-config should be
> safe and not affect other targets:

Adding a new architecture doesn't seem like a simple bug fix or
security problem, so I'm inclined to say no to this.

Ross

Re: Danny stable release branch

[Otavio Salvador]

On Wed, Oct 31, 2012 at 1:28 PM, Burton, Ross <ross.burton@intel.com> wrote:

> Hi Marcin,
>
> On 26 October 2012 16:05, Marcin Juszkiewicz
> <marcin.juszkiewicz@linaro.org> wrote:
> > Are there chances that AArch64 related changes which are present in
> > master can get into danny? Everything other then gnu-config should be
> > safe and not affect other targets:
>
> Adding a new architecture doesn't seem like a simple bug fix or
> security problem, so I'm inclined to say no to this.
>

I second your point of view; besides many fixes or improvements will
involve packaging new recipe versions or adding patches. Since ARMv8 is not
yet public avaiable in SoCs the work could be done in master and don't risk
breaking Danny.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: Danny stable release branch

[Marcin Juszkiewicz]

W dniu 31.10.2012 16:28, Burton, Ross pisze:
> Hi Marcin,
> 
> On 26 October 2012 16:05, Marcin Juszkiewicz 
> <marcin.juszkiewicz@linaro.org> wrote:
>> Are there chances that AArch64 related changes which are present in
>> master can get into danny? Everything other then gnu-config should
>> be safe and not affect other targets:
> 
> Adding a new architecture doesn't seem like a simple bug fix or 
> security problem, so I'm inclined to say no to this.

Thanks for answer. I understand your point and will adapt to it. We will
discuss future or our OE builds during next hour and will probably go with
one revision per week or something like that to minimize amount of
possible breakups.

Re: Danny stable release branch

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Op 26-10-12 15:44, Burton, Ross schreef:
> Hi,
> 
> Now that 1.3 is released[1] I can announce that I'm the Danny stable 
> release series maintainer.  This involves pulling any relevant security
> fixes, build fixes and critical bug fixes from master, and periodically
> rolling a 1.3.x release.
> 
> Obviously there's a lot of activity in master so whilst I intend to 
> consider every commit, if anyone submits patches to master that should 
> also be in danny, please say so either in a direct mail or with a tag in
> the subject line.
> 
> Expect to see a ross/danny-next series in the poky-contrib repository 
> fairly soon where I'll be staging the commits.

Who's the maintainer for the oe-core danny branch?



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org

iD8DBQFQiqmCMkyGM64RGpERAqlNAKCuxa65EGpCO4bpPPdCTmF/GCfooACghbBo
L5cf18xRG5Hjd+DbSiKtrb8=
=uUNb
-----END PGP SIGNATURE-----

Re: [oe] Danny stable release branch

[Burton, Ross]

On 26 October 2012 16:17, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Expect to see a ross/danny-next series in the poky-contrib repository
>> fairly soon where I'll be staging the commits.
>
> Who's the maintainer for the oe-core danny branch?

Shush, don't tell anyone, but poky-contrib:ross/danny-next would
actually be a clone of oe-core. </whisper>  Staging a branch for
oe-core using poky commits would be counter-productive.

I'm handling the stable releases of oe-core 1.3.x, not Poky 8.x.  Poky
point releases are a natural consequence of the oe-core point
releases, but not the goal.

Some how the existence of openembedded-core-contrib slipped my mind
when I wrote this first mail.  Expect a ross/danny-next to appear
instead there once I have push access.

Ross

Re: Danny stable release branch

[Burton, Ross]

On 26 October 2012 16:17, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Expect to see a ross/danny-next series in the poky-contrib repository
>> fairly soon where I'll be staging the commits.
>
> Who's the maintainer for the oe-core danny branch?

Shush, don't tell anyone, but poky-contrib:ross/danny-next would
actually be a clone of oe-core. </whisper>  Staging a branch for
oe-core using poky commits would be counter-productive.

I'm handling the stable releases of oe-core 1.3.x, not Poky 8.x.  Poky
point releases are a natural consequence of the oe-core point
releases, but not the goal.

Some how the existence of openembedded-core-contrib slipped my mind
when I wrote this first mail.  Expect a ross/danny-next to appear
instead there once I have push access.

Ross

Re: [oe] Danny stable release branch

[Otavio Salvador]

On Fri, Oct 26, 2012 at 1:17 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Op 26-10-12 15:44, Burton, Ross schreef:
>> Hi,
>>
>> Now that 1.3 is released[1] I can announce that I'm the Danny stable
>> release series maintainer.  This involves pulling any relevant security
>> fixes, build fixes and critical bug fixes from master, and periodically
>> rolling a 1.3.x release.
>>
>> Obviously there's a lot of activity in master so whilst I intend to
>> consider every commit, if anyone submits patches to master that should
>> also be in danny, please say so either in a direct mail or with a tag in
>> the subject line.
>>
>> Expect to see a ross/danny-next series in the poky-contrib repository
>> fairly soon where I'll be staging the commits.
>
> Who's the maintainer for the oe-core danny branch?

I hope there's no delta between oe-core and poky one so Ross is the
maintainer as far as I know.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: Danny stable release branch

[Otavio Salvador]

On Fri, Oct 26, 2012 at 1:17 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Op 26-10-12 15:44, Burton, Ross schreef:
>> Hi,
>>
>> Now that 1.3 is released[1] I can announce that I'm the Danny stable
>> release series maintainer.  This involves pulling any relevant security
>> fixes, build fixes and critical bug fixes from master, and periodically
>> rolling a 1.3.x release.
>>
>> Obviously there's a lot of activity in master so whilst I intend to
>> consider every commit, if anyone submits patches to master that should
>> also be in danny, please say so either in a direct mail or with a tag in
>> the subject line.
>>
>> Expect to see a ross/danny-next series in the poky-contrib repository
>> fairly soon where I'll be staging the commits.
>
> Who's the maintainer for the oe-core danny branch?

I hope there's no delta between oe-core and poky one so Ross is the
maintainer as far as I know.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: [oe] Danny stable release branch

[Burton, Ross]

On 26 October 2012 16:35, Otavio Salvador <otavio@ossystems.com.br> wrote:
>> Who's the maintainer for the oe-core danny branch?
>
> I hope there's no delta between oe-core and poky one so Ross is the
> maintainer as far as I know.

Correct. Poky is literally oe-core+bitbake+yocto-docs glued together,
no work happens in the poky repository directly, just the "upstream"
repositories.

Ross

Re: Danny stable release branch

[Burton, Ross]

On 26 October 2012 16:35, Otavio Salvador <otavio@ossystems.com.br> wrote:
>> Who's the maintainer for the oe-core danny branch?
>
> I hope there's no delta between oe-core and poky one so Ross is the
> maintainer as far as I know.

Correct. Poky is literally oe-core+bitbake+yocto-docs glued together,
no work happens in the poky repository directly, just the "upstream"
repositories.

Ross