On Scmbug

[Mark Reibert]

On Mon, 2004-06-21 at 09:43, Kristis Makris wrote:
> > The problem with that approach is that it becomes unmanageable for
> large 
> > installations. If, hypothetically, mozilla.org was to start using cvs
> > integration it would mean that every time a dev with commit rights
> > changes their email address/login, some admin would have to change their
> > cvs->bz mapping too. That means that either you have to hack bz to
> 
> Is that a bad thing ? Is the bz email changing, or is the scm integration
> email changing, causing a respective change in the bz email/login ? 
> 
> Besides, bz could keep a chain of email addresses and eventually accept integration requests to older email addresses. Is it a good policy to simply trash older email addresses  used as logins in bz ?

Are we missing the obvious solution? The e-mail address should be an
attribute (or metadata or whatever you want to call it) associated with
the bz account; it should not be the account name/login itself. Then I
can change me e-mail address all I want and never have to worry about
updating the mapping between bz and revision-control tool X.

I am sure there is a reason why bz prefers the often-changing e-mail
address as the primary account information. Maybe the reason is no more
complex than it really doesn't matter until you try to provide automated
integration between bz and another tool?

Mark

-- 

----------------------
Mark S. Reibert, Ph.D.
mark at reibert.com
----------------------