yocto 1.3 branch for meta-openembedded layers, RFC wanted.

yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Koen Kooi]

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

Hi,

We need a branch to track oe-core 'danny' and I am swamped till ELC-E
happens, so I would like to hold off on patches that make meta-oe layers
incompatible with oe-core 'danny'.

As for branch maintenance: any volunteers for managing the meta-openembedded
'danny' branches? There doesn't need to be a single maintainer, but it would
be nice to have one person coordinating everything, even if it's just
pulling in danny-next branches from the layer maintainers every week or so.

As I said above, I'm swamped for the next 3 weeks, so can people who have
used or are using the 'denzil' branch weigh in with feedback/anecdotes/etc?
I have such a document for oe-core 'denzil', which I keep failing to send
out, but it boils down to "better predictability for merge windows". Please
share your experience for meta-oe here.

regards,

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

iD8DBQFQiRqzMkyGM64RGpERAschAJ98yscNYLI9qNGRviDm+drBquLttACgoa0X
/YhGdFr+iYLy8n99sXb4zKE=
=ahtL
-----END PGP SIGNATURE-----

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]

On Thu, Oct 25, 2012 at 12:55:47PM +0200, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> We need a branch to track oe-core 'danny' and I am swamped till ELC-E
> happens, so I would like to hold off on patches that make meta-oe layers
> incompatible with oe-core 'danny'.

Agreed, I never used denzil, but I plan to stick official SHR builds to danny 
branches (because I fear mandatory OEBasicHash in master soon).

> As for branch maintenance: any volunteers for managing the meta-openembedded
> 'danny' branches? There doesn't need to be a single maintainer, but it would
> be nice to have one person coordinating everything, even if it's just
> pulling in danny-next branches from the layer maintainers every week or so.

I can take care of meta-efl and co-maintain the rest too. 

Speaking of meta-efl I've upgrade to bugfix release 1.7.1 + EFL_SRCREV 
bump ready for master in my branch, but plan to test it more, so not sure 
if I should hold it off for longer and then backport it or test it faster :).

Cheers,

> As I said above, I'm swamped for the next 3 weeks, so can people who have
> used or are using the 'denzil' branch weigh in with feedback/anecdotes/etc?
> I have such a document for oe-core 'denzil', which I keep failing to send
> out, but it boils down to "better predictability for merge windows". Please
> share your experience for meta-oe here.
> 
> regards,
> 
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> 
> iD8DBQFQiRqzMkyGM64RGpERAschAJ98yscNYLI9qNGRviDm+drBquLttACgoa0X
> /YhGdFr+iYLy8n99sXb4zKE=
> =ahtL
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Khem Raj]

Hi Koen

I can take care of danny 

Thanks
-Khem

On Oct 25, 2012, at 3:55 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> We need a branch to track oe-core 'danny' and I am swamped till ELC-E
> happens, so I would like to hold off on patches that make meta-oe layers
> incompatible with oe-core 'danny'.
> 
> As for branch maintenance: any volunteers for managing the meta-openembedded
> 'danny' branches? There doesn't need to be a single maintainer, but it would
> be nice to have one person coordinating everything, even if it's just
> pulling in danny-next branches from the layer maintainers every week or so.
> 
> As I said above, I'm swamped for the next 3 weeks, so can people who have
> used or are using the 'denzil' branch weigh in with feedback/anecdotes/etc?
> I have such a document for oe-core 'denzil', which I keep failing to send
> out, but it boils down to "better predictability for merge windows". Please
> share your experience for meta-oe here.
> 
> regards,
> 
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> Comment: GPGTools - http://gpgtools.org
> 
> iD8DBQFQiRqzMkyGM64RGpERAschAJ98yscNYLI9qNGRviDm+drBquLttACgoa0X
> /YhGdFr+iYLy8n99sXb4zKE=
> =ahtL
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Philip Balister]

On 10/25/2012 06:55 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> We need a branch to track oe-core 'danny' and I am swamped till ELC-E
> happens, so I would like to hold off on patches that make meta-oe layers
> incompatible with oe-core 'danny'.
>
> As for branch maintenance: any volunteers for managing the meta-openembedded
> 'danny' branches? There doesn't need to be a single maintainer, but it would
> be nice to have one person coordinating everything, even if it's just
> pulling in danny-next branches from the layer maintainers every week or so.
>
> As I said above, I'm swamped for the next 3 weeks, so can people who have
> used or are using the 'denzil' branch weigh in with feedback/anecdotes/etc?
> I have such a document for oe-core 'denzil', which I keep failing to send
> out, but it boils down to "better predictability for merge windows". Please
> share your experience for meta-oe here.

What is happening on this front? Since oe-core dropp qt-4.8.1, builds 
including meta-oe are now broken.

If the branch maintainers are not ready to go, we need to apply patches 
that fix builds, even if thy break compatibility with Danny.

Philip

>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>
> iD8DBQFQiRqzMkyGM64RGpERAschAJ98yscNYLI9qNGRviDm+drBquLttACgoa0X
> /YhGdFr+iYLy8n99sXb4zKE=
> =ahtL
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
>

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Martin Jansa]

[-- Attachment #1: Type: text/plain, Size: 1781 bytes --]

On Wed, Nov 21, 2012 at 08:11:29AM -0500, Philip Balister wrote:
> On 10/25/2012 06:55 AM, Koen Kooi wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi,
> >
> > We need a branch to track oe-core 'danny' and I am swamped till ELC-E
> > happens, so I would like to hold off on patches that make meta-oe layers
> > incompatible with oe-core 'danny'.
> >
> > As for branch maintenance: any volunteers for managing the meta-openembedded
> > 'danny' branches? There doesn't need to be a single maintainer, but it would
> > be nice to have one person coordinating everything, even if it's just
> > pulling in danny-next branches from the layer maintainers every week or so.
> >
> > As I said above, I'm swamped for the next 3 weeks, so can people who have
> > used or are using the 'denzil' branch weigh in with feedback/anecdotes/etc?
> > I have such a document for oe-core 'denzil', which I keep failing to send
> > out, but it boils down to "better predictability for merge windows". Please
> > share your experience for meta-oe here.
> 
> What is happening on this front? Since oe-core dropp qt-4.8.1, builds 
> including meta-oe are now broken.

And meta-oe needs to have
http://patches.openembedded.org/patch/38519/
applied also for danny (even with my last question still not answered).

But without it at least navit lost gypsy and some other layers could
also assume that gypsy is somewhere in oe-core+meta-oe.

> If the branch maintainers are not ready to go, we need to apply patches 
> that fix builds, even if thy break compatibility with Danny.

In worst case danny branch can be created from revision before qt4-4.8.1
bbappends are dropped.

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Eric Bénard]

Hi Koen,

Le Thu, 25 Oct 2012 12:55:47 +0200,
Koen Kooi <koen@dominion.thruhere.net> a écrit :
> As for branch maintenance: any volunteers for managing the meta-openembedded
> 'danny' branches? There doesn't need to be a single maintainer, but it would
> be nice to have one person coordinating everything, even if it's just
> pulling in danny-next branches from the layer maintainers every week or so.
> 
> As I said above, I'm swamped for the next 3 weeks, so can people who have
> used or are using the 'denzil' branch weigh in with feedback/anecdotes/etc?
> I have such a document for oe-core 'denzil', which I keep failing to send
> out, but it boils down to "better predictability for merge windows". Please
> share your experience for meta-oe here.
> 
if wanted I can continue to handle denzil and also danny branches (and
should have more time than for denzil).

Eric

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Eric Bénard]

Hi Khem,

Le Fri, 26 Oct 2012 08:14:06 -0700,
Khem Raj <raj.khem@gmail.com> a écrit :
> I can take care of danny 
> 
fine I can provide some help if needed (and should have read all the
mail before replying to the previous one ;-)

Eric

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Khem Raj]

Hi Eric

If you have time thats good please go ahead with danny too. I have been
away for most of time after ELCE

Thanks
-Khem


On Wed, Nov 21, 2012 at 7:17 AM, Eric Bénard <eric@eukrea.com> wrote:

> Hi Koen,
>
> Le Thu, 25 Oct 2012 12:55:47 +0200,
> Koen Kooi <koen@dominion.thruhere.net> a écrit :
> > As for branch maintenance: any volunteers for managing the
> meta-openembedded
> > 'danny' branches? There doesn't need to be a single maintainer, but it
> would
> > be nice to have one person coordinating everything, even if it's just
> > pulling in danny-next branches from the layer maintainers every week or
> so.
> >
> > As I said above, I'm swamped for the next 3 weeks, so can people who have
> > used or are using the 'denzil' branch weigh in with
> feedback/anecdotes/etc?
> > I have such a document for oe-core 'denzil', which I keep failing to send
> > out, but it boils down to "better predictability for merge windows".
> Please
> > share your experience for meta-oe here.
> >
> if wanted I can continue to handle denzil and also danny branches (and
> should have more time than for denzil).
>
> Eric
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Otavio Salvador]

On Wed, Nov 21, 2012 at 2:34 PM, Khem Raj <raj.khem@gmail.com> wrote:
> Hi Eric
>
> If you have time thats good please go ahead with danny too. I have been
> away for most of time after ELCE

I am also fine with Eric being the maintainer.

I can be a backup if need.

Regards,

-- 
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: yocto 1.3 branch for meta-openembedded layers, RFC wanted.

[Koen Kooi]

Op 21 nov. 2012, om 21:28 heeft Otavio Salvador <otavio@ossystems.com.br> het volgende geschreven:

> On Wed, Nov 21, 2012 at 2:34 PM, Khem Raj <raj.khem@gmail.com> wrote:
>> Hi Eric
>> 
>> If you have time thats good please go ahead with danny too. I have been
>> away for most of time after ELCE
> 
> I am also fine with Eric being the maintainer.
> 
> I can be a backup if need.

Can you guys cook up a patch to the README changing the requirements from 'master' to 'danny' for oe-core and replace me with the contact info for all the danny maintainters?

regards,

Koen