New version of SOGo was released. Version 2 and 3 will be maintained by SOGo project. I have committed devel/sope3, www/sogo3 and www/sogo3-activesync ports recently. I think that the best is rename www/sogo, devel/sope and devel/sogo-activesync the same way like other ports are stored on ports tree (mysql55, mysql56, etc). It reflect the current version of these ports. It needs new entries on ports/MOVED and ports/UPDATING files devel/sope2 update to 2.3.9 can be obtained from https://people.freebsd.org/~acm/ports/sope2.diff
(In reply to Jose Alonso Cardenas Marquez from comment #0) I agree with your renaming strategy. That was what I intended to do about the two releases. How do we go about this? Who's job is it to do the renaming? Also, I have an update for 2.3.10 coming very soon (today probably). How should I proceed with a PR for the upgrade patch?
A commit references this bug: Author: acm Date: Mon May 2 23:03:07 UTC 2016 New revision: 414486 URL: https://svnweb.freebsd.org/changeset/ports/414486 Log: - Rename devel/sope to devel/sope2 - Update to 2.3.10 PR: 208405 Submitted by: me Approved by: maintainer (Euan Thoms <euan at potensol.com>) Changes: head/devel/Makefile head/devel/sope2/ head/devel/sope2/Makefile head/devel/sope2/distinfo head/devel/sope2/files/patch-configure