On 03/30/2012 06:09 PM, Koen Kooi wrote:

Op 19 mrt. 2012, om 14:05 heeft Tom Rini het volgende geschreven:

On Mon, Mar 19, 2012 at 05:02:47PM -0400, Denys Dmytriyenko wrote:
On Mon, Mar 19, 2012 at 01:58:54PM -0700, Tom Rini wrote:
On Mon, Mar 19, 2012 at 01:58:36PM +0100, Koen Kooi wrote:
Hi,

Any volunteers for maintaining a releasebranch that matches the upcoming 
oe-core release in ~4 weeks?

If Denys or Chase don't step-up, I'll do it.  As qualification, I do
such a thing for oe-classic currently :)  But if either of them would
rather, I'll defer to them.

We'll probably need to set meta-oe-maintenance up anyway for meta-arago to
work with, rather than chasing changes in the master...

Yes, meta-oe will also need a maintenance release to match

meta-oe branch is really close to having a maintainer, what's the (final) word 
on the meta-ti branch?

I have no objection to the branch to ensure the current working functionality remains working with yocto maintenance releases.

However, I don't think we should actively maintain new features on both branches.

So what is the goal of the branch?
_______________________________________________
meta-ti mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-ti

Reply via email to