GNOME Bugzilla – Bug 677404
Patch for Evolution-Data-Server API changes
Last modified: 2012-06-26 16:31:24 UTC
Created attachment 215569 [details] [review] Adapt to Evolution-Data-Server API changes Evolution-Data-Server just landed some major API changes in an effort to get off of GConf and overhaul the way it stores account information. I blogged about this recently with more details: http://mbarnes.livejournal.com/4631.html I'm trying to provide patches to affected modules. Here's yours. This bumps the libebook requirement to >= 3.5.3.
Looks fine to commit after a branching a gnome-3-6 branch off of the gnome-3-0 one.
I take this to mean you'll handle the branching and I'll commit after?
Any progress? We have an upcoming 3.5.3 release (tarball due is on jun 26) and I hope we can include the new Evolution stuff.
I didn't get exactly what Bastien was asking for in comment #1. Seems premature for a gnome-3-6 branch but I can do whatever's needed to commit this.
I don't want revert all evolution stack to previous release, so Matthew if you want and can please branch, commit (and make a new release?) otherwise I'll do it (while I didn't have time to apply and check the patch itself) > Seems premature for a gnome-3-6 branch FWIK nautilus-sendto is currently in "maintainance only" mode, so branching now should be fine.
(In reply to comment #5) > I don't want revert all evolution stack to previous release, so Matthew if you > want and can please branch, commit (and make a new release?) otherwise I'll do > it (while I didn't have time to apply and check the patch itself) I'd rather you didn't do this sort of thing without talking to the maintainers in the future. > > Seems premature for a gnome-3-6 branch > FWIK nautilus-sendto is currently in "maintainance only" mode, so branching now > should be fine. It's got nothing to do with that. master is the unfinished new UI, you shouldn't branch off of master.
(In reply to comment #2) > I take this to mean you'll handle the branching and I'll commit after? I meant that you should do this, but it seems that the nautilus-sendto branching is a bit too complicated. I've created the branch, and bumped the version. I don't have an updated e-d-s build, so somebody else will have to apply your patch and do the release.
(In reply to comment #6) > (In reply to comment #5) > > I don't want revert all evolution stack to previous release, so Matthew if you > > want and can please branch, commit (and make a new release?) otherwise I'll do > > it (while I didn't have time to apply and check the patch itself) > > I'd rather you didn't do this sort of thing without talking to the maintainers > in the future. Well, it seems that both me and Matthew tried to talk with and have a reply from you in the past two weeks, I'm not eager to bypass maintainers and take care of their duty, but please remember that release team follow the "just do it" policy when needed.
Patch applied and 3.5.3 released.
(In reply to comment #8) > Well, it seems that both me and Matthew tried to talk with and have a reply > from you in the past two weeks, I'm not eager to bypass maintainers and take > care of their duty, but please remember that release team follow the "just do > it" policy when needed. I receive tons of bugzilla mail. Talk to me instead of getting bugzilla to send more spam. You might even be able to get someone on the release team that knows my whereabouts...-