Integrating upstream kernel bugzilla into distro kernel bugzilla?

[Deepak Saxena <dsaxena@xxxxxxxxxxx>]

The subject basically says it all. I'm working on inproving the way
we handle "continious product engineering", i.e. bug-hunting on
older distro kernels and one of the cases that comes up is where
the bug still exists in the upstream kernel but our patch against
2.6.old is not valid as the code has been re-written, re-architected,
etc. We've had an unfortunate history of fixing those bug in our
maintaince branch and not getting around to fixing it upstream
until we do a new merge (currently every 12-18 months but that
will be changing that to follow the development cycle heartbeat) 
and I'm looking for a way to mark a bug as "needs fixing upstream",
assiging to our CPE engineer, and track it to completion. I'm going 
to encourage our CPE developers to start using the upstream bugzilla in 
those cases but would like a way to tie that data into our bugz database. 
I'm not a bugzilla expert so wondering what others might be doing in 
this area?  I've heard mention of having cross-distro kernel bugzilla 
and also wondering if there is still any interest in this?

Tnx,
~Deepak (MontaVista kernel patch-monkey)

-- 
Deepak Saxena - dsaxena@xxxxxxxxxxx - http://www.plexity.net

In the end, they will not say, "those were dark times,"  they will ask
"why were their poets silent?" - Bertolt Brecht
-
To unsubscribe from this list: send the line "unsubscribe kernel-packagers" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html