All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [layerindex-web][PATCH 000/242] Integrate and improve Recipe Reporting System (cover letter only)
Date: Wed, 02 May 2018 08:09:06 +1200	[thread overview]
Message-ID: <3282715.K8pGKosiL1@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <8a00c2aa-ea4a-bc9f-65e7-4df683420169@linux.intel.com>

Hi Alex,

On Tuesday, 1 May 2018 9:58:03 PM NZST Alexander Kanavin wrote:
> On 05/01/2018 05:23 AM, Paul Eggleton wrote:
> > The Recipe Reporting System (RRS - live instance at
> > http://recipes.yoctoproject.org) was originally developed as a fork of
> > the layer index (live instance at http://layers.openembedded.org) - this
> > set of changes rebases it on top of master and makes the functionality
> > possible to activate for other layers. I've introduced the concept of a
> > "Maintenance Plan" to tie together the recipe maintenance information
> > for one or more layers and used it to replace all the parts that assumed
> > Poky or OE-Core were the repositories/layers being tracked. I've also
> > made it possible again for the application to gather data going back to
> > 1.6 across the python 2/3 divide, and made various cleanups and
> > optimisations in the code.
> 
> Thanks! Is this already taken into use on the recipes.yoctoproject.org?

No, what you see there is still the old version. I haven't discussed it yet 
with Michael but I would propose that once this gets merged and 
layers.openembedded.org is updated, then recipes.yoctoproject.org would simply 
become a redirect to the OE-Core maintenance plan on layers.openembedded.org.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




  reply	other threads:[~2018-05-01 20:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-01  2:23 [layerindex-web][PATCH 000/242] Integrate and improve Recipe Reporting System (cover letter only) Paul Eggleton
2018-05-01  9:58 ` Alexander Kanavin
2018-05-01 20:09   ` Paul Eggleton [this message]
2018-10-02 21:50     ` Anibal Limon

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=3282715.K8pGKosiL1@peggleto-mobl.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=alexander.kanavin@linux.intel.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.