[Xesam] Xesam 1.0 vs Xesam 2.0

[Arun Raghavan]

On Tue, Oct 7, 2008 at 5:35 PM, Mikkel Kamstrup Erlandsen
<mikkel.kamstrup at gmail.com> wrote:
[...]
> Yes, it makes sense to keep the breakage between 1.0 and 2.0 as
> minimal as possible.

My main thoughts on this ("borrowed", as you can no doubt see):

1) Release early, release often: get the spec out and let people have
something stable to use

2) Make one to throw away: it's okay if some things need to change
radically over the API after the first version. If comaptibility can
remain, that's good, but let's deal with that particular problem when
we get to it. As Mikkel says, if there is a compelling reason to use
the newer API, clients will get (re)written switch to it. And there
are always ways to make that transition less painful.

My 2p,
-- 
Arun Raghavan
(http://nemesis.accosted.net)
v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056
e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com