Re: [egit-dev] Bugzilla principles

[Benjamin Muskalla <bmuskalla@xxxxxxxxxxxxxxxxx>]

Hi,

looking at the trend in bugzilla, we try to "tag" our bugs for
different components (eg, Repo view, Sync View, etc). As EGit is
becoming more complex, it is pretty normal that such subcomponents are
introduced.

I'd suggest to follow the idea of different projects to "tag" bugs
properly with a component. Personally, I really like this as it allows
me to have a quick view on all relevant bugs that are open for the
component I'm currently working on (eg. Sync View).

Take a look at these bugs as example:
JDT: http://www.eclipse.org/jdt/ui/doc/bug-annotation.php
RAP: http://preview.tinyurl.com/368z3gw
Mylyn: http://preview.tinyurl.com/2uj9m6u

I'd love to use tags like this for egit bugs and therefor suggest
these three for the beginning (more can be added when we need them):
[sync] - everything related to Synchronize / Synchronize View
[repoView] - everything related to the Git Repository View
[releng] - for build issues

Any objections or thoughts from your side?

Regards,
 Ben

On Fri, Aug 6, 2010 at 9:43 AM, Lay, Stefan <stefan.lay@xxxxxxx> wrote:
>> Hey,
>>
>> another thing that came up today. Do we already have a set of
>> principles
>> how to use Bugzilla?
>>  From my expierence in the last years working on RAP and using the
>> bugzilla there, we came up with several things that had done a good job
>> in the past.
>>
>> Things like:
>> * Always tag your fixed bugs with a Target Milestone to get a proper
>> list of fixed things at the release date (eg.
>> http://eclipse.org/rap/noteworthy/1.4/news_M1.php - there is a link to
>> show all bugs for the M1 milestone).
>> * Assign bugs to yourself when working on it and cc the global inbox.
>> Assigning is a small problem is nobody else gets mail notifications on
>> changes. That's why we set the rap-inbox as cc to bugs we assign to
>> ourselves.
>>
>> I think we should come up with some guidelines how to use bugzilla (if
>> there are no already discussed) and write them down in the wiki.
>>
>
> +1 from me
>
> Is there a good source of information about best practices at eclipse? I know http://wiki.eclipse.org/Architecture_Council/Bugzilla_Best_Practices, but the statement " Bugzilla best practices are under re-investigation" did not encourage me to read it. There was a discussion on bug 288393 also, but it stopped one year ago.
>
> Stefan
> _______________________________________________
> egit-dev mailing list
> egit-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/egit-dev
>