Apologies for the tardy response.
cc'ing Mikko as he's also interested in the pkgdb work and especially who
manages what metadata.
cc'ing Ramez as he may want to capture this requirement for the pkgdb
cc'ing Stephen as he knows about the bugzilla API
On 22/06/11 18:59, Andre Klapper wrote:
CC'ing David Greaves.
On Thu, 2011-06-16 at 06:25 +0000, [email protected] wrote:
It seems that there has been lots of changes in the MeeGo, and I have
started to wonder if the default QA contacts and Assignees are correct
anymore. Facing the problem in every Bug Triage I’m in. Also there’s
people in the CC lists who aren’t working with/for MeeGo or the
component/project anymore.
I think it’s time to check the all BMC components to make sure that
the information is correct.
@David:
As you proposed linking the package database grouping and the Bugzilla
grouping in the EM BoF session[1] at MeeGo Conf SF:
Does or could the package database grouping also contain info about
default assignees and maintainers for a certain package?
Does : No
Could : Yes
Should: ?
As I mentioned at the SF conference on a couple of occasions; MeeGo has no-one
looking at the overall data architecture. Individual systems overlap at the data
level and of course every system should "naturally" be where the master for all
the data in that system is stored :)
In this case Bugzilla would 'naturally' be the master for assignees and
maintainers for a certain package. Unless of course we tried to have a
package-centric view when we expect to see the team roles in the package DB. Or
we could look at the build view when the OBS also naturally holds maintainer and
bugowner information...
One solution to this is to have a data warehouse approach with the warehouse
being used to support queries and synchronisation wherever possible. Another is
to have a mesh of system to system synchronisation. Both approaches have pros
and cons.
I'm wondering if at least the default assignee in MeeGo Bugzilla could
be kept up-to-date by this - it might fix one aspect of the problem
described above by Iekku.
I'm not saying it "should" but I'm fairly sure it could - does the Bugzilla API
allows this Stephen?
So to answer this question we should start to look at who manages various role
assignments and where would they best be mastered.
The important thing here is that it doesn't matter where the data is mastered as
long as we are able to maintain it. That means reports, alerts and change processes.
So how does the default assignee/maintainer for a package change? Is it easiest
at that point to change data in BZ or some other system? (Eg if the change
happens as part of handling a bug requesting a change then BZ is easy to update;
if it happens when modifying the packageDB then jumping out to BZ is a bad idea).
David
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
_______________________________________________
MeeGo-qa mailing list
[email protected]
http://lists.meego.com/listinfo/meego-qa
