[OTR-dev] Hmmm.

[Ian Goldberg]

So I came across a small bug in gaim-otr: when you're presented with an
unknown fingerprint, the gaim-otr dialog says:

    l33thax0r (IRC) has presented us with an unknown fingerprint.

But of course that's not enough information to identify who we're
talking about, since there may be different l33thax0r's on different IRC
networks.  It really should say:

    l33thax0r (IRC) has presented k00lk1d at irc.freenode.net with an
    unknown fingerprint.

This is easy to fix.  Unfortunately, it requires a small change in the
libotr API (the function that handles unknown fingerprints needs to take
an additional argument (the account name)).

I'd do this in a heartbeat, except now we've got versioning rules about
changing the API, so this would mean the release of libotr 2.0.0.

Is there any reason not to do that?  Am I just having silly hangups
about increasing the major number for a relatively small bugfix (but one
that incompatibly changes the API)?  I could also wait a little bit and
see if Evan or the proxy work shows up any other changes that can be put
into 2.0.0 at the same time.  [Evan shouldn't release his Adium code
until 2.0.0 is out, and then he should use that (and display the account
name, which will then be delivered to him).  So that's an argument for
"sooner, rather than later".  So is "release early, release often".]

[In other news, I just got a AM_PATH_LIBOTR autoconf macro working,
and the proxy is now autoconfiscated and using it.  :-) ]

So: release often, or hold off?

   - Ian