Hello, If I can elaborate on Martin request, as well if there is a proper procedure for updating from nightly 3.x to production/stable 4.x (via subscription) on the same server or if it is better to export data, nuke the old install, and install again.
Cheers, Raimondo On Monday, March 05, 2018 00:49 CET, Martin Waschbüsch (mar...@waschbuesch.de) <users@sogo.nu> wrote: Hi Ludovic, Am 01.03.2018 um 14:52 schrieb Ludovic Marcotte (lmarco...@inverse.ca) <users@sogo.nu>: Hello, Early next week, we'll release SOGo v4. We've been working hard on this release for many months. Among some of important features of SOGo v4, there are: * full S/MIME support for signing and encryption * complete rework of the handling of recurrence exceptions * performance optimizations of the Web GUI by creating AngularJS components * many Enterprise ActiveSync improvements We also made a gazillion of bug fixes and improvements. Nightly builds of the upcoming v4 have been available since the beginning of the week - just replace /3/ by /4/ in the URL for the repositories while we update the website for the releaseThat is awesome! Are there instructions for the upgrade procedure yet? Any major things to look out for? e.g. required changes in SQL backend, etc. Martin-- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
