From owner-freebsd-ports@FreeBSD.ORG Mon Jul 21 09:17:16 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD84737B401 for ; Mon, 21 Jul 2003 09:17:16 -0700 (PDT) Received: from histidine.utmb.edu (histidine.utmb.edu [129.109.65.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id F1DA243FA3 for ; Mon, 21 Jul 2003 09:17:15 -0700 (PDT) (envelope-from bdodson@scms.utmb.EDU) Received: from histidine.utmb.edu (localhost [127.0.0.1]) by histidine.utmb.edu (8.12.9/8.12.9) with ESMTP id h6LGHB6d006638; Mon, 21 Jul 2003 11:17:11 -0500 (CDT) (envelope-from bdodson@histidine.utmb.edu) Received: (from bdodson@localhost) by histidine.utmb.edu (8.12.9/8.12.9/Submit) id h6LGHA1L006635; Mon, 21 Jul 2003 11:17:10 -0500 (CDT) From: "M. L. Dodson" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16156.4614.625777.649884@histidine.utmb.edu> Date: Mon, 21 Jul 2003 11:17:10 -0500 To: noackjr@alumni.rice.edu In-Reply-To: <3F1B6FCC.8010700@alumni.rice.edu> References: <3F1B6FCC.8010700@alumni.rice.edu> X-Mailer: VM 7.14 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: freebsd-ports@freebsd.org Subject: Re: maintainer timeout? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: bdodson@scms.utmb.EDU List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jul 2003 16:17:17 -0000 Jon Noack writes: > How long should one wait on a maintainer? I've emailed them directly > and they said they would take care of updating the port "tonight". That > was 5 days ago. The latest version of the software was released almost > 2 months ago, and fixed major stability issues. A whole host of vendor > patches have been released *since then* that have fixed 2 Major (vendor > terms), 4 Medium, and various other issues. There have been several > outstanding PRs that are several weeks old and one that is 4 months old > (although it is for the version currently in the port, not the latest > version). > > There was a previous commit by a non-maintainer after a ~3 month timeout > (same maintainer). I'm not sure I have the expertise to take over the > port, but I don't know what else to do now. > > Any guidance would be appreciated, > Jon Noack If the maintainer is not also a committer, then the delay is to be expected. I estimate I have about a 6 weeks average from the time I submit a PR for an update until it is committed. Unfortunate, but "them's the breaks". Be patient. Or negotiate with the maintainer to take over the port. Bud Dodson -- M. L. Dodson bdodson@scms.utmb.edu 409-772-2178 FAX: 409-772-1790