From nobody Mon Mar 04 01:16:49 2024 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Tp14x1wngz5CjL8 for ; Mon, 4 Mar 2024 01:17:05 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Received: from udns.ultimatedns.net (udns.ultimatedns.net [24.113.41.81]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "ultimatedns.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Tp14w2m7Kz4p12 for ; Mon, 4 Mar 2024 01:17:04 +0000 (UTC) (envelope-from portmaster@bsdforge.com) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of portmaster@bsdforge.com has no SPF policy when checking 24.113.41.81) smtp.mailfrom=portmaster@bsdforge.com Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.16.1/8.16.1) with ESMTP id 4241Govv038852; Sun, 3 Mar 2024 17:16:56 -0800 (PST) (envelope-from portmaster@bsdforge.com) List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 Date: Sun, 03 Mar 2024 17:16:49 -0800 From: Chris To: Xin LI Cc: freebsd-ports@freebsd.org Subject: Re: Proposed ports deprecation and removal policy In-Reply-To: References: User-Agent: UDNSMS/17.0 Message-ID: X-Sender: portmaster@bsdforge.com Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_ip X-Spamd-Result: default: False [0.00 / 15.00]; MIME_GOOD(-0.10)[text/plain]; ONCE_RECEIVED(0.10)[]; R_SPF_NA(0.00)[no SPF record]; local_wl_ip(0.00)[24.113.41.81]; FREEMAIL_TO(0.00)[gmail.com]; ASN(0.00)[asn:11404, ipnet:24.113.0.0/16, country:US]; R_DKIM_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+] X-Rspamd-Queue-Id: 4Tp14w2m7Kz4p12 On 2024-03-02 17:48, Hubert Tournier wrote: > On Thu, 29 Feb 2024 19:26:23 UTC, Xin LI wrote: > >> For example, one of my port gets marked as DEPRECATED because a dependency >> was deprecated and scheduled for removal after 1 month, without any email >> telling me so (the port doesn't have a lot of releases and there isn't any >> release during that "parole" month), and it gets removed after that. So in >> order to know there is an ongoing deprecation of the port, I as a port >> maintainer would have to either watch the directory for any changes, or >> read all ports-git commit messages or at least a filtered version of it, >> and that's burdensome and inefficient use of developer time at best. > >> What I would love to see happen is that, when a port gets marked as >> DEPRECATED, there is an automated system that sends me notification with >> something like: > >> ACTION REQUESTED: X new ports you maintain is marked as DEPRECATED > > [...] > >> and that email gets sent every 7 days until the port is removed or the >> issue is fixed. Or a bug is created and assigned to the maintainer, etc. IMHO Depreciation should performed via pr(1) -- the bugzliia bug reporting system we already use for bugs. I'm on the commits-ports-all@ list which is a noisy list. I'm maintain over 100 ports, so it seems justified. But someone with a dozen or less ports, joining ports-all list would probably seem too large a burden. We want to encourage participation, not discourage it. Bugzilla should be the required path for DEPRECIATION. All maintainers are already notified automatically. So this seems like the most efficient path for all concerned. -- Chris Hutchinson