On Fri, 2012-06-01 at 15:48 -0400, Matthew Barnes wrote: > The backend-facing APIs less so. They tend to see more churn anyway, > even without my branch. I can't think of a recent release where the > backend APIs didn't change a little. And that's fine -- the damage is > contained -- but we still have to go touch all the backends for every > API change and some of those aren't trivial. And especially with this > new E-D-S architecture I've cooked up, which is an improvement but > still far from perfect, I think we'll be seeing a rash of backend API > changes over the next few devel cycles. So I'm not really buying the > "toy" argument.
Hi, OK, I suppose we can always reincarnate it when there will be enough user demand on it. The last backend API changes seemed to me as not that complicated, at least those I helped with (on review and backend adaptation parts), kind of monkey work there, but I agree that some changes can be harder to test. What about a "compromise", drop support for evolution-exchange when 3.7.x development begins? I suppose it'll be fair to have the main API changes done and any potential community person taking care of it will not need to learn all the hard changes being done during 3.5.x, thus it'll be lighter start for him/her/them. Bye, Milan _______________________________________________ evolution-hackers mailing list evolution-hackers@gnome.org To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers