Tracking enhancements/wishlist items (was "junior kernel tasks")

Eitan Adler lists at
Thu Oct 30 06:19:54 UTC 2014

On 29 October 2014 16:00, Garrett Cooper <yaneurabeya at> wrote:
>> On Oct 29, 2014, at 13:53, Marcus von Appen <mva at> wrote:
> ...
> If we are going to do that, the area however should be
>> separate from typical "bugs", so people do not confuse wishes with bugs
>> and vice versa.  Also, to avoid long and misleading comment trails, we
>> would need the ability to hide/remove errornous (bug-related) comments
>> in the wishlist (a feature wished for independent of this, but a
>> necessary prerequisite [probably coming soon]).
>> Wishlist items thus should not belong to a currently existing product or
>> component, but should be clearly classified in an own product and/or
>> component category.
>> Except from that, what else would be required and desired to have a
>> suitable wishlist? The bug tracker right now features:
>> - tags
>> - keywords
>> - links to internal bugs/items (dependencies and blockers)
>> - links to external systems
>> - links to svn commits and reviews
>> - attachments
>> - flags to request/confirm/deny things
> At $work we use Enhancement in the severity field to generally denote these kinds of items. However, we could always use wishlist in the Keywords field.
> All I ask for is a centralized place to track this or easy way to look this up instead of 10+ wiki pages and doc pages full of outdated/incorrect material.

I don't object to an 'Enhancement' section of the bug tracker.  This
is far better than split trackers.

Generally, I've found that using bug trackers for wishlist items leads
to other discoverability problems, but if we manage to solve that,
then it isn't terrible.

Eitan Adler

More information about the freebsd-current mailing list