From nobody Mon Jul 17 07:22:55 2023 X-Original-To: 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 4R4D7y6FSDz4nH1G for ; Mon, 17 Jul 2023 07:23:10 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R4D7y4Zmkz3GyJ for ; Mon, 17 Jul 2023 07:23:10 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lj1-x22c.google.com with SMTP id 38308e7fff4ca-2b933bbd3eeso25767871fa.1 for ; Mon, 17 Jul 2023 00:23:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689578589; x=1692170589; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=u4Oho9G4yj3twc8RwkH0FvfnjTss/R7Mfv3/G/uowmw=; b=DgruZfZKKykVxuBMqce/52pp8gXgILSGDayEfWCXWQnIh5kmrClQs1BLSRvfX0puIe 2CTp6T+tg7/BrQ66Jdhf36NnVbva/VTleynGqkUo/7MTc0BDVPL9u7M7RT625ZN+lIgp 5DkFnNh15+CW3+j6fR0hJpo1AMDq4pSEb2gdbBf4APxNpc38tT6bL9yeaDHcnlw1k5wc nKgMA/hm6BoHP7Z5frg8ALvq7/rOf+li/pHp+DegIf6ijRmPecbnGkca1fe8snovd2f4 /LlWNRtUQXPi11JVlStxZpUso4ROhGzwGyL3JY2/k9wGsS9QxsZygq9P028H+k3C+FxI q3ag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689578589; x=1692170589; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=u4Oho9G4yj3twc8RwkH0FvfnjTss/R7Mfv3/G/uowmw=; b=dQXGugLtg9IbQkNyMcbYFKmSj9np/u0rVDTY8u8zOUh8hMeOiEzDrvTZqWyeKyfDrS XmoREOORgXOAG/YwgUJ0rPNjFQ8+rm9BnlopQXPjJBlUsuY7RS92pQMUrHIAsWC9C8fa 4v34/HXkv0offaxiC4JaHqOmeUO4U2h5qET6NjmA5hjM2PnHuI9MrC+VcvOEiibPgfAs SDy+jZikNMswPbkcOEkQBsZbL42gf0dmwCWi1/tjidJyANW1u5siVcKn2+NhmnUKqHHG KDiCFU9LnP2pdp16chEfpwJEPGm9Pbje4V02Gew1NY3INgtov5+kKif85Tj0Qq70L1Ok 3Qeg== X-Gm-Message-State: ABy/qLazD99GUVPV+oVC3+NHY5IgPaLqK8Uj/CtP9ski/D6gROZg52C1 tTD7YoVZ2+kfsiP/W94UGQiixZNBWUsAdd6p4IVKf1wnvQjUEQ== X-Google-Smtp-Source: APBJJlEOX6mgh8ZEwqWLamf0nOhDditQRcA/meiz+7tb2ZZ3fZba9FvtCQ95uHcAPJXJP3XUbIvzVvMI93O+DH8u2+g= X-Received: by 2002:a2e:86c6:0:b0:2b4:737c:e316 with SMTP id n6-20020a2e86c6000000b002b4737ce316mr10419316ljj.14.1689578588493; Mon, 17 Jul 2023 00:23:08 -0700 (PDT) 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 References: <6D24E23B-1F79-47E9-B533-361188502BEA@lassitu.de> In-Reply-To: <6D24E23B-1F79-47E9-B533-361188502BEA@lassitu.de> From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= Date: Mon, 17 Jul 2023 09:22:55 +0200 Message-ID: Subject: Re: Can someone please post a concise list of things maintainers are supposed to do? To: Stefan Bethke Cc: ports@freebsd.org Content-Type: multipart/alternative; boundary="000000000000965bfc0600a9ab39" X-Rspamd-Queue-Id: 4R4D7y4Zmkz3GyJ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000965bfc0600a9ab39 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Jul 17, 2023 at 9:04=E2=80=AFAM Stefan Bethke wrot= e: > Hi, > > every time I submit a PR to update a port I maintain, I get conflicting > instructions about how to fill in the PR. This is really annoying, and so= me > committers apparently feel they will not move forward in processing the P= R > unless some bureaucratic bullshit is done. > > Can the ports team please provide a concise, definitive list on how a > maintainer is supposed to fill in a port update PR, so this nonsense stop= s? > Hi Stefan, Having the PR database in good shape is important. It makes it more searchable and helps with consistency. The canonical information on how to properly fill a PR is in the resources found at https://www.freebsd.org/support/bugreports/ Some port specific tips would be: - If Reporter is MAINTAINER, set *maintainer-approval* attachment flag value to + (#teach) - Do not set maintainer-feedback unless to avoid maintainer timeout or if it was requested first. - - Version update: - - *Check for upstream changelog URL, add to URL field * Bugfix or security release: Set *merge-quarterly* flag to ? - * Security release: Request VuXML entry (#teach) - If port Makefile gives an error, specify target in summary, like: Fails to : $error-summary Cheers. > > > Thanks, > Stefan > > -- > Stefan Bethke Fon +49 151 14070811 > > --000000000000965bfc0600a9ab39 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Mon, Jul 17, 2023 at 9:04=E2=80=AF= AM Stefan Bethke <stb@lassitu.de&g= t; wrote:
Hi,
every time I submit a PR to update a port I maintain, I get conflicting ins= tructions about how to fill in the PR. This is really annoying, and some co= mmitters apparently feel they will not move forward in processing the PR un= less some bureaucratic bullshit is done.

Can the ports team please provide a concise, definitive list on how a maint= ainer is supposed to fill in a port update PR, so this nonsense stops?
<= /blockquote>

Hi Stefan,

Hav= ing the PR database in good shape is important. It makes it more searchable= and helps with consistency.

The canonical inf= ormation on how to properly fill a PR is in the resources found at https://www.freebsd.org/su= pport/bugreports/

Some port specific tips woul= d be:

  • If Reporter is MAINTAINE= R, set maintainer-approval attachment flag value to + (#teach)

  • Do not set maintainer-feedback unless to avoid maintainer tim= eout or if it was requested first.

  • Version update:

    • =C2=A0*Check for upstream changelog URL, add to URL field

    =C2= =A0* Bugfix or security release: Set merge-quarterly flag to ?

  • =C2=A0* Security release: Request VuXML entry (#teach) =

  • If port Makefile gives an error, specify target in s= ummary, like: Fails to <target>: $error-summary

    • Cheers.=


    Thanks,
    Stefan

    --
    Stefan Bethke <stb@l= assitu.de>=C2=A0 =C2=A0Fon +49 151 14070811

    --000000000000965bfc0600a9ab39--