All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Yocto Project Discussion <yocto@yoctoproject.org>
Subject: Recipe maintainer-ship and distro_tracking_fields.inc
Date: Fri, 08 Apr 2011 10:06:48 -0700	[thread overview]
Message-ID: <4D9F40A8.3070902@linux.intel.com> (raw)



Yocto Project Contributors,

Please review and comment on this.

As we we move forward, we are trying to keep track of who is maintaining 
the recipes and what version tracking is, as not all upstream 
information can be tracked automatically, so we have been using a 
distro_tracking_fields.inc file located in meta/conf/distro/include.

This file is used not only for tracking version information, but also by 
the Package Database (http://packages.yoctoproject.org), so that people 
that use the Yocto Project they can see License and Version information 
via a web interface.

We will also use it to generate reminder emails as upstream packages are 
updated to update the recipes (if appropriate) or mark in the 
distro_track_fields.inc file that it should not be updated. By keeping 
the RECIPE_MAINTAINER information current, this will help to improve the 
quality and currentness of core recipe meta-data.

 From time to time recipe ownership changes, if you are interested in 
contributing to the Yocto Project recipes as part of core or other 
layers, then please take a look at the who the current maintainer is and 
let them know you would like to help.  When you do that and the current 
owner replies, please update the distro_tracking_fields.inc with your 
name as RECIPE_MAINTAINER.

As the Yocto Project wants to keep the to the most current stable 
release of the upstream projects, the maintainers will receive email 
during the development milestones reminding them to update their recipes 
as appropriate. This will also be tracked by the core maintainers, if a 
recipe is not updated in a timely manner, the core maintainers may 
update it directly. If the recipe maintainer is unable to continue 
updating their recipes beyond 1 release, the core maintainers may choose 
to re-assign the recipe, so the recipe does not become stale.

http://wiki.yoctoproject.org/wiki/Distro_Tracking

-- 
     Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System



                 reply	other threads:[~2011-04-08 17:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4D9F40A8.3070902@linux.intel.com \
    --to=sgw@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.