[gentoo-dev] Re: Referencing bug reports in git

[Duncan]

Gordon Pettey posted on Mon, 10 Aug 2015 17:57:56 -0500 as excerpted:

> On Mon, Aug 10, 2015 at 7:25 AM, Duncan <1i5t5.duncan@×××.net> wrote:
>
>> ** summary bug number standardized to GB#xxxxxx or #xxxxxx or similar,
>> short enough for summary, easily identified. GB# would be distinctly
>> gentoo and could be expanded to KDEB#, GNB# (gnome), FDOB#, etc, for
>>
>>
> If you're going to prepend the project, just spell it out.

My thought is that this is the one-line summary, generally limited to 75 
chars, including category/package.  Spelling it out thus takes precious 
character-space that can better be used to describe the problem in words.

> Don't add a B suffix to everything. If it's the same everywhere, then
> it is meaningless, and just confuses things.

Very good point, particularly in light of the above -- that's another 
character-slot from 75 that can't be used for other things.

> Don't prefix bugs with #. 1. It doesn't apply to every system: Random
> Project using Jira is going to have bugs like RP-123. You'd have to
> insert it in the middle of the identifier like RP-#123. 2. It is a
> relatively useless prefix at best: In the bug tracker UI, you search for
> 123, not #123. At worst, it makes the identifier invalid (as in the Jira
> example).

Once again, very good point.  Thanks. =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman