Date: Thu, 22 Aug 2024 09:17:05 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 280905] [NEW PORT] net/asterisk20: Latest LTS version of Asterisk PBX software Message-ID: <bug-280905-7788-P5orlq1573@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280905-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-280905-7788@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=3D280905 Guido Falsi <madpilot@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madpilot@FreeBSD.org --- Comment #4 from Guido Falsi <madpilot@FreeBSD.org> --- Hi, I stumbled on this by chance. I'd like to share a little insight. As a former maintainer for asterisk, while I agree I have no right to manda= te anything I'd like to suggest to avoid recreating multiple asterisk ports wi= th version numbers in the port, especially if they are going to be maintained = by different people. If this is the new LTS, the main net/asterisk port should be updated to it = and if keeping the previous LTS around is deemed really really really important, that one should be moved to a versioned port. The maintenance burden on asterisk can get important easily, so having mult= iple versions in the tree is expensive in maintainer/committer workload terms. Just two cents. (I did drop asterisk maintainership because I has not been using it anymore= for years and still not using it, so I have no horse in this race anymore) --=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-280905-7788-P5orlq1573>