Date: Thu, 26 Jul 2018 08:34:43 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 230051] lang/php70 please MFH latest update to 2018Q3 Message-ID: <bug-230051-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230051 Bug ID: 230051 Summary: lang/php70 please MFH latest update to 2018Q3 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: tz@freebsd.org Reporter: rainer@ultra-secure.de Assignee: tz@freebsd.org Flags: maintainer-feedback?(tz@freebsd.org) Hi, I hope this does not sound like a rant and I don't want to sound too nagging but it's a security update after all. AFAIK, the maintainer has the right to MFH for php 7.1 + 7.2 but not for 7.0 (last time we chatted). There may be reasons for this but two days turnaround time should be enough. Or what is the expected time for an MFH that the maintainer has no right to commit? I know "we" don't have an SLA on ports-commits etc, but it would still be g= ood to have some sort of ball-park number on how fast one can expect an MFH. This would at least save me time I spend on reloading the svnweb page. Apologies if I missed something obvious (i.e. it's written somewhere). I "freeze" the quarterly cut build after some time, before I roll it out to= my hosts - and I'd like the lastest php update in. Thanks in advance --=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-230051-7788>