From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project Discussion <yocto@yoctoproject.org>,
yocto-infrastructure@yoctoproject.org
Subject: Re: Bugzilla Re-organization
Date: Fri, 1 Jun 2012 16:03:46 -0400 [thread overview]
Message-ID: <4FC92022.4080402@windriver.com> (raw)
In-Reply-To: <4FC8FF2E.3060701@linux.intel.com>
On 12-06-01 01:43 PM, Darren Hart wrote:
>
>
> On 05/31/2012 08:37 PM, Bruce Ashfield wrote:
>> On 12-05-31 2:27 PM, Darren Hart wrote:
>>>
>>>
>>> On 05/25/2012 03:38 PM, Michael Halstead wrote:
>>>> The first draft of the reorganized bugzilla is available for feedback
>>>> now at https://bugzilla.yoctodev.org/. Outgoing e-mail is currently
>>>> disabled on this preview copy. Please feel free to take a look and see
>>>> if you spot any errors. Additional refinement of product or component
>>>> descriptions will be helpful as well.
>>>>
>>>
>>> It seems to me one should be able to find the linux-yocto kernel itself
>>> under the Yocto Project Components from the basic search page. Currently
>>> there is Kernel Tooling and BSPs, but there are times when the bug is
>>> not BSP specific and is in the kernel itself, not the tooling. For this,
>>> a hierarchy like the following might be preferable:
>>>
>>> Yocto Project Components
>>> BSPs
>>> bsps
>>> Kernel
>>> linux-yocto
>>> configuration
>>> kernel-tooling
>>
>> +1. I completely agree with this.
>>
>>>
>>> I am still not sure how best to deal with BSPs here and BSPs in Build
>>> System& Metadata. I think We should pick one or the other as the
>>> distinction between the two is non-obvious (actually I have no idea what
>>> it would be).
>>
>> Agreed .. that this is hard. If we used 'configuration' for the kernel
>> category, could the build system + meta data fall into that as well
>> under BSPs ?
>>
>> i.e.
>>
>> BSPs
>> bsps - runtime
>> bsps - configuration
>
> I think so. I like this better.
>
> Tom, any objections?
>
> Yocto Project Components
> BSPs
> bsps-runtime
> bsps-configuration
> Kernel
> linux-yocto
> kernel-configuration
> kernel-tooling
>
> The other Kernel related path would include
> Build System& Metadata
> Layers - OpenEmbedded-Core
> kernel
>
> This would be for the kernel.bbclass and other recipes and classes.
>
> I think we should just kill:
> Build System& Metadata
> Layers - BSPs
>
> and move all the BSP components under Yocto Project Components->BSPs
>
> Finally there is:
>
> Build System& Metadata
> Layers - meta-yocto
> machines
>
> Which should just go away and be replaced witha BSPs->meta-yocto
> component, if anything.
>
> So, the final layout would be:
>
> Yocto Project Components
> BSPs
> bsps-runtime
> bsps-configuration (these top too being "generic" buckets)
> bsps-meta-yocto
> bsps-meta-fsl-ppc
> bsps-meta-intel
> bsps-meta-ti
> bsps-tools
> bsps-xilinx (meta-xilinx?)
>
> Kernel
> linux-yocto
> kernel-configuration
> kernel-tooling
>
> I believe this would make it much easier for us to manage Kernel related
> issues across the project.
Agreed. This makes sense to me.
+1
Bruce
>
> --
> Darren
>
>
>>
>> ?
>>
>> Bruce
>>
>>>
>>> Tom, Bruce: opinions on the above?
>>>
>>>
>>> "Build System& Metadata" and "Yocto Metadata Layers" use different
>>> naming schemes for the components in the various layers products. Some
>>> use meta- others do not.
>>>
>>>
>>
>
next prev parent reply other threads:[~2012-06-01 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 22:38 Bugzilla Re-organization Michael Halstead
2012-05-28 5:28 ` Damian, Alexandru
2012-05-30 14:51 ` Rifenbark, Scott M
2012-05-30 15:12 ` Michael Halstead
2012-05-31 18:27 ` Darren Hart
2012-06-01 3:37 ` Bruce Ashfield
2012-06-01 17:43 ` Darren Hart
2012-06-01 20:03 ` Bruce Ashfield [this message]
2012-06-01 17:45 ` Darren Hart
2012-06-01 21:33 ` Tom Zanussi
2012-06-01 21:42 ` Darren Hart
2012-06-01 21:47 ` Tom Zanussi
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=4FC92022.4080402@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=yocto-infrastructure@yoctoproject.org \
--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.