I made the change to reuse the existing
cbi-inbox@xxxxxxxxxxx so if you just follow that one you
should now get new bugs coming in no matter what component the bug
was opened against.
Thanh
On 17/03/14 02:13 PM, Thanh Ha wrote:
There are 3 inboxes listed below. You have a good point though regarding just putting everything in 1 inbox considering low amounts of traffic we get. I will see if it's too much trouble to make that change after I return from EclipseCon.
_____ Bugzilla Components _____
1. [webmaster] Create these bugzilla components.
Name: maven-plugins
Description: Maven plugins for signing
Owner: cbi.maven-plugins-inbox@xxxxxxxxxxx
Name: signing-service
Description: Eclipse Signing Service (Server Side)
Owner: cbi.signing-service@xxxxxxxxxxx
Name: license
Description: License features
Owner: cbi.license@xxxxxxxxxxx
Thanh
On 15/03/14 05:49 PM, David M Williams wrote:
Apologies if
there's easier ways of finding this out --- or already
discussed and decided.
I recently opened a bug in CBI
(under "license" component), and noticed it's "in-box" was cbi.license@xxxxxxxxxxx.
Does each component follow that
same pattern?
Perhaps it's "too much trouble"
to change and this point, but I would have suggested just one
in-box for anything in "CBI" ... make it easier to subscribe
to "watch for" any new bug in CBI.
But, if the "component"' format
was deliberately adopted, that's fine, and I'll just subscribe
to each. (But, then makes it harder to know if/when a new
component was added).
But, also didn't know, that
perhaps "license" was the only exception to "cbi-inbox@xxxxxxxxxxx"?
Thanks,
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cbi-dev
|
