On Mon, 16 Apr 2007, Alan Burlison wrote:
Paul Jakma wrote:
On Mon, 16 Apr 2007, Alan Burlison wrote:
What happens when the Solaris bug is changed? How does that propagate to
the external bug? What happens when the external bug changes? How does
that propagate to the Solaris bug?
A human must copy the values over.
They won't. And in the case of non-Sun people, they can't anyway.
Sorry, I meant only the case where the Solaris bug is updated (with
the overriding presumption that the external bug is the upstream
one).
It's the same bug, not two bugs. You are confusing artefacts of
the proposed implementation with reality - a bug is a single thing,
not two. Or more.
I'm not, and it's actually 3 things:
- The bug, maintained in the upstream DB
- The reference in the downstream DB to the bug, to allow
users of the downstream DB to more easily track bugs without
replication
- Integration status information, private to the downstream DB
(of no relevance to the general bug / upstream).
So what happens for external distributions? Where do they store *their*
distribution-specific data?
In their bug systems.
Viewing isn't sufficient, you need to be able to edit both, at the same
time. And commit the changes to both, atomically.
I dont think that can fly.
Distributed databases are a well-understood technology that has been around
for a very long time. Of course it can fly.
Indeed, and to date conflict resolution in such systems /still/
ultimately requires human input (some conflicts can be automated, but
you still need humans).
OpenSolaris is not a distribution. Solaris, Nextenta, Schillix...
are. They will all need to cooperate on bugs whilst preserving
their own private data.
Right.
OpenSolaris would be be both upstream and downstream for different
bugs. If the 'bug reference' links can allow for transitive use, that
shouldn't be a problem.
Humans suck at this sort of thing. They need to be kept out of the
loop as far as possible, not made into an integral part of the
process.
That would rock. Unfortunately I've no ideas on how to do that.
I can see some small stuff that can be easily automated (as in
earlier email), but the distributed-bug/integration-DB thing - I've
no clue, sorry. ;)
regards,
--
Paul Jakma [EMAIL PROTECTED] [EMAIL PROTECTED] Key ID: 64A2FF6A
Fortune:
Anti-trust laws should be approached with exactly that attitude.
_______________________________________________
tools-discuss mailing list
[email protected]
