From: Darren Hart <darren.hart@intel.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Wold, Saul" <saul.wold@intel.com>
Subject: Re: Results of latest documentation audit, May 2011
Date: Fri, 06 May 2011 14:36:12 -0700 [thread overview]
Message-ID: <4DC469CC.2040209@intel.com> (raw)
In-Reply-To: <4DC45A26.3090900@intel.com>
On 05/06/2011 01:29 PM, Scott Garman wrote:
> Hello,
>
> As a data point for where we stand in ensuring our packages are
> producing documentation, I have some scripts which build all recipes
> (using the output of bitbake -s, not world), and then check that a -doc
> package is generated which is populated with files.
>
> A summary of the results using yesterday's master are as follows:
>
> 591 recipes in total
> 308 recipes are building documentation
> 283 recipes are not building documentation
>
> 31 recipes did not build (and are counted as not building documentation
> above).
>
> The lists of recipes are attached to this email. We'd like to improve
> the percentage of recipes that produce documentation (separated into
> -doc packages, of course) for our next major release in October.
>
> Our userspace recipe maintainers should look into setting aside some
> time to know which of their recipes are in the "not building
> documentation" list and work to improve them. A lot of this is likely to
> be low-hanging fruit.
>
I see "linux-*" in the list. What sort of documentation are we looking
for? The linux-image* packages in Ubuntu, for example, include a
changelog and a copyright.
Thanks,
--
Darren
> Thanks,
>
> Scott
>
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-06 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 20:29 Results of latest documentation audit, May 2011 Scott Garman
2011-05-06 21:36 ` Darren Hart [this message]
2011-05-06 23:53 ` Scott Garman
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=4DC469CC.2040209@intel.com \
--to=darren.hart@intel.com \
--cc=saul.wold@intel.com \
--cc=scott.a.garman@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.