From owner-freebsd-ports-bugs@freebsd.org Thu Jul 26 08:34:46 2018 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE2501047BC2 for ; Thu, 26 Jul 2018 08:34:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 5B09785297 for ; Thu, 26 Jul 2018 08:34:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 208301047BC0; Thu, 26 Jul 2018 08:34:45 +0000 (UTC) Delivered-To: ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D2D71047BBE for ; Thu, 26 Jul 2018 08:34:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2D7B85294 for ; Thu, 26 Jul 2018 08:34:44 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id F164FD827 for ; Thu, 26 Jul 2018 08:34:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6Q8Yh4u015215 for ; Thu, 26 Jul 2018 08:34:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6Q8Yh5O015212 for ports-bugs@FreeBSD.org; Thu, 26 Jul 2018 08:34:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 230051] lang/php70 please MFH latest update to 2018Q3 Date: Thu, 26 Jul 2018 08:34:43 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rainer@ultra-secure.de X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: tz@freebsd.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jul 2018 08:34:46 -0000 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.=