Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhCOz-00A9Xl-KT for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2024 17:47:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rhCOy-009nuJ-6U for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2024 17:47:00 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rhCOx-009nuB-W0 for pgsql-www@lists.postgresql.org; Mon, 04 Mar 2024 17:47:00 +0000 Received: from mail-ej1-x634.google.com ([2a00:1450:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rhCOv-002l07-Ia for pgsql-www@postgresql.org; Mon, 04 Mar 2024 17:46:59 +0000 Received: by mail-ej1-x634.google.com with SMTP id a640c23a62f3a-a4515f8e13cso186807566b.3 for ; Mon, 04 Mar 2024 09:46:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f10-com-br.20230601.gappssmtp.com; s=20230601; t=1709574416; x=1710179216; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZC/FSbMQlZysanbv8V8VFrLava69pHFT8DQzFkVjM0M=; b=gXK8v/rMlyFXFbVqX/BEWHfqCgP+vNb02LZSC9A/g6GBjfPMcLHfFP2J4q638k+4do SfpPiNhO6lpl36DQUxWcdVfKc5qUTVPC2p240mWyqrOlVVP0Q5EUxkRoDLEU3KI06a+a zaynIwetsmojM9ooXSM99SYaoh1OaiRG4fAmsjUcxTMe9hvDmi/kW48nK+QRae8f0EAf LN5Y3+ZtPT9Op6Er9N/d1r5e4J72qKsMQV098gx0iND4vq2xPHI4mSmgi/rcIwqx4Z1o uKF/5cjmAxJVrLYznx5PUp3zSdL+HvHHavN512wKYm4T3We3cHjo8vCYJtkgOUdHP2QC qZWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709574416; x=1710179216; 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=ZC/FSbMQlZysanbv8V8VFrLava69pHFT8DQzFkVjM0M=; b=Q6RonNlfv6wl+l5NzWh5HeZ7OeE5TF45LW36MswR6LWkGELdI6eMTzV5r9ZKjQcdG4 /Fv9KYn1/UVD6BPfzX0SVbMGuXvBVxJOEB04UA7MuORP9QCo7cwCI0LAq30m0+jDKFd5 BCf4XxItMYYNJltglAIxj90KVlZf/L0cbSBy9L/4ZipVpCl3eXvNK4bwb9t/R1iNRo8r 7VRxSIgPwzA92I1CHlRnwL/0Cl5qSEEEIRx8cFBsOawUirDbaFSRxTiGn0F+b53ABfOr JssT7+XruJLD1AdJdZXb6TfxYUOmsvUt4MlDcdNV4WDB+O+tHGTeq36zkj5frQSYs2K8 L1+A== X-Forwarded-Encrypted: i=1; AJvYcCU7iY4UeyTm8nbiwQoQDU8ynFH+mwY2nSsgMBP4sTSiZzAUy1CEGrMee8sxbrmGrDyOmr50h/Emr8wvZUQVu13Kk1W0zqOMfUQ= X-Gm-Message-State: AOJu0YyDMv4dfmrEKOBboAdrHbXerxFZQ9svSqJ5dytmlb+JC33SN2fy IMksa8K2T4gzhNx5PYJCDDoLN/O/NWnSAkSfKBwdb/etoHqXWYf8w90+aktw3cz4rG8dEE9U9Zr ziBZXJB9FF/1F6xb2lWJDBPrbPPnBOVZuEnuL X-Google-Smtp-Source: AGHT+IEfuxIwd+D9I7kOJbQBiPR9+bQcI16mtKWoeoMMlAlN0+fSiogy8YG5bPIdb1aSdH/vRhKeSX79nWKIks/P3YQ= X-Received: by 2002:a17:906:33d8:b0:a45:52af:7397 with SMTP id w24-20020a17090633d800b00a4552af7397mr1993510eja.44.1709574416395; Mon, 04 Mar 2024 09:46:56 -0800 (PST) MIME-Version: 1.0 References: <202403021444.yyabqn4eatpx@alvherre.pgsql> <3597695.1709565152@sss.pgh.pa.us> In-Reply-To: <3597695.1709565152@sss.pgh.pa.us> From: Marcos Pegoraro Date: Mon, 4 Mar 2024 14:46:08 -0300 Message-ID: Subject: Re: Diff of this page with other version To: Tom Lane Cc: Euler Taveira , Daniel Gustafsson , Alvaro Herrera , pgsql-www@postgresql.org Content-Type: multipart/alternative; boundary="000000000000ce850a0612d94feb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ce850a0612d94feb Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Em seg., 4 de mar. de 2024 =C3=A0s 12:12, Tom Lane escr= eveu: > Given that we've not offered something like this > at all before, I think it's silly to put in a lot of up-front effort > in advance of seeing what the demand really is. > Well, only saying that I brought to this discussion several committers is proof of how beneficial this feature would be. > In any case, I concur with the other committers that there is simply > no way we're going to accept manual change markup as an additional > expectation for documentation commits. It's hard enough already. I understand that every change on docs would have this additional step, but I don't think it is a huge step. And talking about additional steps, compare how many tags exist on release notes of version 8.0 and release notes of version 16.0. --000000000000ce850a0612d94feb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Em seg., 4 de mar. de 2= 024 =C3=A0s 12:12, Tom Lane <tgl@ss= s.pgh.pa.us> escreveu:
=C2=A0
Give= n that we've not offered something like this
at all before, I think it's silly to put in a= lot of up-front effort
in advance of seeing what the demand really is.

Well, only saying that= I brought to this discussion several committers=C2=A0
is proof of how beneficial this feature would be.
=C2=A0
In any case, I concur with the other committers that there is simply
no way we're going to accept manual change markup as an additional
expectation for documentation commits.=C2=A0 It's hard enough already.

I un= derstand that every change on docs would have this additional step,
but I don't think it is a huge step. And talking about = additional=C2=A0steps,=C2=A0
compare how many tags e= xist on release notes of version 8.0 and=C2=A0
relea= se notes of version 16.0.=C2=A0


--000000000000ce850a0612d94feb--