On Mon, 2012-08-06 at 21:18 +0200, tino.keitel+syncevolution(a)tikei.de wrote: True. I probably should just go ahead and tag+compile 1.2.99.4. Or perhaps go for 1.3 directly? What do you and users think? Does 1.3 need more time for testing or should I just go ahead and pull the trigger? There's no real roadmap. I'd like to release 1.3 when it's ready. The recent discovery of some issues (like the broken auto sync) seem to imply that it's not quite there yet, but that's just anecdotal evidence. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

On Tue, 2012-08-07 at 12:24 +0200, tino wrote: I tagged 1.2.99.4 this morning, a sanity build + test run is on-going. Renaming it to 1.3 will require another recompile, because the version number is embedded in the configure script and resulting binaries. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

On Wed, 2012-08-08 at 11:41 +0200, Patrick Ohly wrote: I've added that check and re-ran a full test. I also included the fix for the libdbus timeout. Are there any other unsolved problems that need to be addressed in 1.3? I'm aware of only one issue which kind of blocks releasing 1.3: in testing ActiveSync against Google, occasionally activesyncd gets confused about the default folders, resulting in errors about "Sync error: Fetch or Change operation that has an id no longer valid on the server". I thought I had tracked it down and fixed, but it still failed again in the latest test run. This is not necessarily a blocker, because it only seems to occur in the first sync against the server and goes away when retrying. Nethertheless I'll probably spend some time tomorrow to look again at this problem. Then the next step would be to tag 1.3 and test/compile binaries over the weekend. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

On Thu, 2012-08-30 at 15:39 +0200, Ove Kåven wrote: I have a fix that I am okay with, and it is in the "master" branch of libsynthesis that will be used for 1.3. I don't know yet what Lukas thinks about the patch. Speaking of 1.3, the test run over the weekend crashed the nightly test server, and I am continuing to chase the random activesyncd "empty folder ID" problem. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.