From nobody Fri Jan 5 07:44:05 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 4T5wSv3W93z56QFg for ; Fri, 5 Jan 2024 07:44:15 +0000 (UTC) (envelope-from SRS0=1UwH=IP=klop.ws=ronald-lists@realworks.nl) Received: from smtp-relay-int-backup.realworks.nl (smtp-relay-int-backup.realworks.nl [87.255.56.188]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4T5wSs6FZ6z40QP for ; Fri, 5 Jan 2024 07:44:13 +0000 (UTC) (envelope-from SRS0=1UwH=IP=klop.ws=ronald-lists@realworks.nl) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=klop.ws header.s=rw2 header.b="LNH/FbGR"; dmarc=pass (policy=quarantine) header.from=klop.ws; spf=pass (mx1.freebsd.org: domain of "SRS0=1UwH=IP=klop.ws=ronald-lists@realworks.nl" designates 87.255.56.188 as permitted sender) smtp.mailfrom="SRS0=1UwH=IP=klop.ws=ronald-lists@realworks.nl" Received: from rwvirtual374.colo.realworks.nl (rwvirtual374.colo.realworks.nl [10.0.10.74]) by mailrelayint1.colo2.realworks.nl (Postfix) with ESMTP id 4T5wSj4DmDz1CW; Fri, 5 Jan 2024 08:44:05 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=klop.ws; s=rw2; t=1704440645; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to; bh=jn48tLfYp+WKoKDddAJ4W9luWrzqv+jbXo9Vx735pio=; b=LNH/FbGRz1Uk9N4RQYlBsqDvtaIQxkQwiJ2T5nyBBqTBoyywJH62WSopgp/BE64duQs18y htga6xotM4Lfjv0iN+W5wLEz23Bw33VSO3IPW1EnvSKx1v+dncU49UU6PnmuFOucAQk5o7 gltx4ZirJsqXvVrq8fn0nFm9K6q+CtksLWJL7l36ioWgqKSgPD8HnsO0yHPQB+cZmpRh3y K10jAjEA+l3heHT2sV6RQaFJTTRj2Epeh5S5EuZYeFB5xdFU/Hxhz+neRSCgfKvh8NChw1 VgZTY7ZdnGT4HHfg/DruiCR323u82Yy/2IDK2PRW6wtX+xRHFjxdQl1WatVVng== Received: from rwvirtual374.colo.realworks.nl (localhost [127.0.0.1]) by rwvirtual374.colo.realworks.nl (Postfix) with ESMTP id 5D8CFC01BA; Fri, 5 Jan 2024 08:44:05 +0100 (CET) Date: Fri, 5 Jan 2024 08:44:05 +0100 (CET) From: Ronald Klop To: freebsd-ports@freebsd.org Cc: henrichhartzer@tuta.io Message-ID: <592560205.22819.1704440645198@localhost> In-Reply-To: Subject: Re: Latest and quarterly best practices 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 Content-Type: multipart/alternative; boundary="----=_Part_22818_1577542765.1704440645193" X-Mailer: Realworks (683.54) X-Originating-Host: from (localhost [127.0.0.1]) by rwvirtual374 [10.0.10.74] with HTTP; Fri, 05 Jan 2024 08:44:05 +0100 Importance: Normal X-Priority: 3 (Normal) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.19 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.999]; NEURAL_HAM_SHORT(-1.00)[-0.996]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[klop.ws,quarantine]; FORGED_SENDER(0.30)[ronald-lists@klop.ws,SRS0=1UwH=IP=klop.ws=ronald-lists@realworks.nl]; R_DKIM_ALLOW(-0.20)[klop.ws:s=rw2]; R_SPF_ALLOW(-0.20)[+ip4:87.255.56.128/26]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_TWO(0.00)[2]; RCVD_TLS_LAST(0.00)[]; HAS_X_PRIO_THREE(0.00)[3]; FROM_HAS_DN(0.00)[]; ASN(0.00)[asn:38930, ipnet:87.255.32.0/19, country:NL]; ARC_NA(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_NEQ_ENVFROM(0.00)[ronald-lists@klop.ws,SRS0=1UwH=IP=klop.ws=ronald-lists@realworks.nl]; DKIM_TRACE(0.00)[klop.ws:+]; TO_DN_NONE(0.00)[]; MLMMJ_DEST(0.00)[freebsd-ports@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~] X-Rspamd-Queue-Id: 4T5wSs6FZ6z40QP ------=_Part_22818_1577542765.1704440645193 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Van: henrichhartzer@tuta.io Datum: 4 januari 2024 02:52 Aan: Freebsd Ports Onderwerp: Latest and quarterly best practices >=20 >=20 > Hi, >=20 > I'm not a committer so this shouldn't carry much weight. Just wanted to e= xpress my opinion. >=20 > I think the latest and quarterly setup is a nice and clever one. Unfortun= ately, it seems fairly often that ports that should probably be cherrypicke= d into quarterly are not. Occasionally, some updates make it into quarterly= that don't make clear sense to me, but this is much more rare. >=20 > I propose that as a rule of thumb, if a package uses Semantic Versioning = (semver) and the changes are non-breaking, it should be cherry picked into = quarterly. Especially if this is only a patch level change and not a minor,= but likely either way. >=20 > A couple of recent examples that I've seen, which I would like to point o= ut Please note that I am *not* picking on anyone and this is just what I'm = more familiar with. >=20 > net-p2p/monero-cli was updated from 0.18.2.2_2 to 0.18.3.1 on the 19th of= October. Any software that is blockchain related tends to need to be as cu= rrent as possible for security reasons. Quarterly still has 0.18.2.2_2 (alt= hough 2023Q1 will be cut soon, I assume) which is quite out of date now. >=20 > An opposite case, and this one may be truly a no harm no foul case: x11-w= m/hyprland was updated from 0.33.1_2 to 0.34.0, and cherrypicked to quarter= ly. There were a number of changes in this release, and I personally would = be hesitant to recommend such a cherrypicking unless there were known issue= s with 0.33.1 that users had complained about. Otherwise, since it's an off= line window manager, it seems like waiting for the quarterly release would = make the most sense. Now in this case I don't know the context and cherrypi= cking may have made complete sense -- I'm just using it as an example to tr= y and explain my thoughts. >=20 > Please don't feel at all like I'm being nitpicky. I'm just hoping to cont= ribute how I can and it seems like the processes around cherrypicking could= be improved. I love FreeBSD and appreciate the tremendous amount of work t= hat has gone into it. It really is great because of the contributions of ma= ny I'm just hoping to make it even greater! >=20 > Thank you for reading, and Happy New Year! >=20 > Sincerely, > Henrich >=20 >=20 >=20 >=20 >=20 Thanks for your ideas. There are some guidelines to this. https://wiki.freebsd.org/Ports/QuarterlyBranch But it is not a =E2=80=9Cprocess=E2=80=9D as in somebody is responsible for= this. It is mostly up to the maintainer of the port to cherry-pick. So if you miss something in a Q branch I think it is fastest to: 1- contact the maintainer of the port by mail or PR. 2- contact this ports mailing list. Does this resolve anything of your thoughts? Regards, Ronald. ------=_Part_22818_1577542765.1704440645193 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

Van: henrichhartzer= @tuta.io
Datum: 4 januari 2024 02:52
Aan: Freebsd Ports <freebsd-ports@freebsd.org>
Onderwerp= : Latest and quarterly best practices

Hi,

I'm not a committer so this shouldn't carry much weight. Just wanted to exp= ress my opinion.

I think the latest and quarterly setup is a nice and clever one. Unfortunat= ely, it seems fairly often that ports that should probably be cherrypicked = into quarterly are not. Occasionally, some updates make it into quarterly t= hat don't make clear sense to me, but this is much more rare.

I propose that as a rule of thumb, if a package uses Semantic Versioning (s= emver) and the changes are non-breaking, it should be cherry picked into qu= arterly. Especially if this is only a patch level change and not a minor, b= ut likely either way.

A couple of recent examples that I've seen, which I would like to point out= Please note that I am *not* picking on anyone and this is just what I'm mo= re familiar with.

net-p2p/monero-cli was updated from 0.18.2.2_2 to 0.18.3.1 on the 19th= of October. Any software that is blockchain related tends to need to be as= current as possible for security reasons. Quarterly still has 0.18.2.= 2_2 (although 2023Q1 will be cut soon, I assume) which is quite out of date= now.

An opposite case, and this one may be truly a no harm no foul case: x11-wm/= hyprland was updated from 0.33.1_2 to 0.34.0, and cherrypicked to quar= terly. There were a number of changes in this release, and I personally wou= ld be hesitant to recommend such a cherrypicking unless there were known is= sues with 0.33.1 that users had complained about. Otherwise, since it's an = offline window manager, it seems like waiting for the quarterly release wou= ld make the most sense. Now in this case I don't know the context and cherr= ypicking may have made complete sense -- I'm just using it as an example to= try and explain my thoughts.

Please don't feel at all like I'm being nitpicky. I'm just hoping to contri= bute how I can and it seems like the processes around cherrypicking could b= e improved. I love FreeBSD and appreciate the tremendous amount of work tha= t has gone into it. It really is great because of the contributions of many= I'm just hoping to make it even greater!

Thank you for reading, and Happy New Year!

Sincerely,
Henrich


Thanks for your ideas.

There are some gu= idelines to this.
https://wiki.freebsd.org/Ports/QuarterlyBranch

But it is not a =E2=80=9Cprocess=E2=80=9D as in somebody is res= ponsible for this. It is mostly up to the maintainer of the port to cherry-= pick.

So if you miss something in a Q branch I thi= nk it is fastest to:
1- contact the maintainer of the port by mai= l or PR.
2- contact this ports mailing list.

Does this resolve anything of your thoughts?

Re= gards,
Ronald.


------=_Part_22818_1577542765.1704440645193--