Date: Wed, 20 Jul 2016 21:32:51 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 211237] www/sogo3-activesync: Issues after upgrade to version 3.1.4 Message-ID: <bug-211237-13-vUiFkclpII@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-211237-13@https.bugs.freebsd.org/bugzilla/> References: <bug-211237-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211237 --- Comment #3 from Euan Thoms <euan@potensol.com> --- (In reply to Martin Waschb=C3=BCsch from comment #1) Well, it doesn't surprise me. SOGo release engineering these days is questionable. I've been using SOGo for quite a few years now. It was steadi= ly getting better for a long time. Then suddenly silly bugs started appearing everywhere. I've fixed a couple of them myself, they are very helpful takin= g my patches upstream. I blame the v3 branch development, even the v2 went downh= ill in quality. In my companies production server, where I can't afford regressions, I'm still using 2.2.14 with a couple of backported fixes I do myself. I've tested every v2 version since and there is some nasty regressi= on I can't afford. So for me 2.2.14 was the apex of SOGo quality. I just keep ho= ping that now that the v3 branch is out the door, they will batten down the hatc= hes on the bugs, at least in v2 whereby it's pretty much in maintenance. I did start off by not updating the SOGo ports every single release. At lea= st not without testing in production on my personal server/domain. But I kept getting requests for the latest versions by other port users. Ironically, it was the activesync features that pushed the urgency for some of those users. Likewise, I was not in a rush to port v3, I won't use it myself for a while yet, it's a big regression as far as I'm concerned. But I like where they're going, it just needs more time to mature. Anyways, what I can do is either: (i) Create a patch from the upstream fix (should be accessible from github). (ii) Wait for 3.1.5 to be released. I'm guessing they won't wait long to release, given the severity of the fixed bug. What do other suggest I do? P.S., I've stopped evangalising SOGo for the time being. The project really needs to focus on quality of existing features and forget about new features for a while. Many that use it, like myself, really depend heavily on it bei= ng stable. It's mission critical to our business. I really hope they sort it o= ut soon. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-211237-13-vUiFkclpII>