OK - I just renamed 1.1.1 to 1.2, and 1.2 to 1.3. This means that API changes are OK. Since we're still incubating and don't have a strong user base, it probably doesn't make sense to put a lot of effort into backward compatibility at the moment. In the future, we'll probably want to take a more structured approach.
On Thursday, April 09, 2009, at 02:56PM, "Greg Brown" <[email protected]> wrote: >Realized just after I sent this that this isn't sufficient, because we need to >change the listener interface. Maybe we need to create a 1.1.1 branch. > >On Thursday, April 09, 2009, at 02:54PM, "Greg Brown" <[email protected]> wrote: >>>I would have preferred to maintain backwards compatibility, but the listener >>>API had to be changed anyway. >> >>We don't want to make API changes that would break backwards compatibility in >>maintenance releases. I suggest deprecating the old signature and adding a >>new one. We can remove the old one when we release v1.2. >> >> >> > >
