Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: OE/TSC monthly IRC meeting notes - Apr 1 2014
Date: Tue, 01 Apr 2014 18:56:52 +0100	[thread overview]
Message-ID: <533AFDE4.1080809@communistcode.co.uk> (raw)
In-Reply-To: <533AF862.5000201@linaro.org>



On 01/04/2014 18:33, Trevor Woerner wrote:
> Here are my notes from today's monthly OE/TSC meeting which takes place
> the first Tuesday of every month on freenode's #oe channel.
>
> attendees: bluelightning, Jefro, RP, denix, tlwoerner, fray, nerdboy,
> kergoth
>
> topic #1: upcoming release
> - schedule: https://wiki.yoctoproject.org/wiki/Yocto_1.6_Schedule
> - check RP's email
> http://lists.openembedded.org/pipermail/openembedded-core/2014-April/091378.html
> - test report for rc1 is available:
> https://wiki.yoctoproject.org/wiki/WW13_-_2014-03-26_-_Full_Pass_Release_1.6_M5.rc1
> - optimism for a good 1.6 release
> - enhancements such as READMEs still being accepted
> - bug fixes (such as work on SOBBW issues) still being accepted
> - bug metrics showing downward trend:
> https://wiki.yoctoproject.org/charts/combo.html
>
> topic #2: SOBBW (state of bitbake world) or world build status
> - http://www.openembedded.org/wiki/Bitbake_World_Status
> - fixing items on the list still needs lots of help, helpers needs a way
> to organize themselves to avoid duplication (email, wiki, irc, ...)
> - one cause/issue is people sending patches then disappearing, lots of
> unmaintained recipes
> - possible solutions: meta-nonworking, blacklist.bbclass, smaller "core"
> layer
>
> topic #3: website infrastructure and updates
> - at ELCE2013 plans were made for a new
> http://www.openembedded.org/wiki/Main_Page
> - no plans yet for OE wiki cleanup
> - unfortunately the people working on this weren't available to provide
> an update

Almost there, ka6sox thinks he has the solution for fixing the PHP 
issues we're having, spoke to him regarding it last week and he is on 
track to fix it when he gets back from working away from home.

>
> open topics
> - please make sure any requests for 1.7 are in bugzilla
> - recipe style unification between OE and Yocto Project
>
> action items:
> - RP to look for remnants of BROKEN = "1" (?)
> - fray to move blacklist issue forward with JaMa
> - tlwoerner to sync style guides
>
> next meeting: May 6th 2014, same time, same place
>


      reply	other threads:[~2014-04-01 17:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01 17:33 OE/TSC monthly IRC meeting notes - Apr 1 2014 Trevor Woerner
2014-04-01 17:56 ` Jack Mitchell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=533AFDE4.1080809@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox