From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Troy Hinckley Newsgroups: gmane.emacs.devel Subject: Re: [External] : Re: Emacs 28.3 RC1 testing Date: Mon, 27 Mar 2023 10:12:35 -0600 Message-ID: <604a027a-e74d-4f61-938e-9eaf521ee016@Spark> References: <06c78bbd-0e25-4bd3-bb58-d13e1c5003ac@Spark> <2b2113f6-1e9c-4008-b83b-e17515b2f78e@Spark> <20230318102332.k7imgee3rikiajxq@Charalamposs-MacBook-Air.local> <20230318164948.n3vvjo6utpflaqsw@Charalamposs-MacBook-Air.local> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="6421c078_2cd89a32_2a3" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39731"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Charalampos Mitrodimas , "=?utf-8?Q?emacs-devel=40gnu.org?=" , Lars Ingebrigtsen To: Drew Adams , Eli Zaretskii , Stefan Kangas , Corwin Brust Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 27 18:36:26 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pgppZ-000A2j-Et for ged-emacs-devel@m.gmane-mx.org; Mon, 27 Mar 2023 18:36:25 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pgpop-00078h-6G; Mon, 27 Mar 2023 12:35:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pgpSq-0004zs-FJ for emacs-devel@gnu.org; Mon, 27 Mar 2023 12:12:56 -0400 Original-Received: from sender4-op-o15.zoho.com ([136.143.188.15]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pgpSo-0005Sv-ES; Mon, 27 Mar 2023 12:12:56 -0400 ARC-Seal: i=1; a=rsa-sha256; t=1679933568; cv=none; d=zohomail.com; s=zohoarc; b=TnLRuxc4dcyUB2nunXhzojuVDpqJuWiLDl/hMiHQiLaVl8nh0S1026tFLG+7ajXf089mDqmc2budd41H6ResKx9RHtgkBP9nRCBH6BwPGNqLRNPwP60RSipobCYfTH22pzUgWJTwuUNq/6TlqrQvB2AthSeAm8U6C+Sbt9rrvPU= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1679933568; h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=9GZ1RZwAxvCVoNt7045PI0pD7jur+RPzRG6QsRit98o=; b=FeffOwZSYzLsgn5rWh0ggyvki7QjGq8iHRnKcweU1nZf+COF00Ax2BAXi3Run6yhkNDPAmbFcf9E1mlzcVc6sP98ceqp4PGcbiTcZNAx5Y1yzEK/EgXSq0zLOseBR76cqqkDSnpbkXXM2/ClVcRiXkzvRCDi/XE+zBIKyoMQk8Q= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=dabrev.com; spf=pass smtp.mailfrom=comms@dabrev.com; dmarc=pass header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1679933568; s=zoho; d=dabrev.com; i=comms@dabrev.com; h=Date:Date:From:From:To:To:Cc:Cc:Message-ID:In-Reply-To:References:Subject:Subject:MIME-Version:Content-Type:Message-Id:Reply-To; bh=9GZ1RZwAxvCVoNt7045PI0pD7jur+RPzRG6QsRit98o=; b=RUNJa9fNxZaJ6x0U4+c4RHV4jPmrXMJIqo9QPN4AaymvwN44NIJvgNLQE6yGKGZK AA7vQdOTmTm7YSnJWASibEhbpqDfAzo1paUpfwo/QTr9pGOJaqCv6ugOSEg6XDx237e xVd1axYOUYErE2mFYdcZkaz7Ey+nfBvRRAHj1klY= Original-Received: from [192.168.1.122] (h24-54-181-16.ftcmco.broadband.dynamic.tds.net [24.54.181.16]) by mx.zohomail.com with SMTPS id 1679933566317668.3798572745523; Mon, 27 Mar 2023 09:12:46 -0700 (PDT) In-Reply-To: X-Readdle-Message-ID: 604a027a-e74d-4f61-938e-9eaf521ee016@Spark X-ZohoMailClient: External Received-SPF: pass client-ip=136.143.188.15; envelope-from=comms@dabrev.com; helo=sender4-op-o15.zoho.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-Mailman-Approved-At: Mon, 27 Mar 2023 12:35:37 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:304786 Archived-At: --6421c078_2cd89a32_2a3 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Who needs to sign off to do the release=3F Is that only Eli or Stefan=3F On Mar 18, 2023 at 3:08 PM -0600, Corwin Brust , wrote: > On Sat, Mar 18, 2023 at 2:30=E2=80=AFPM Drew Adams wrote: > > > > > > > The latest RC I see at https://urldefense.com/v3/=5F=5Fhttps://= alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28 > > > > > is RC1, dated 2023-02-19. > > =5Bsnip=5D > > > > Duh. =46or some reason I was seeing the =22rc1=22 in the name > > and not noticing the =2228.3=22 in the name. Thx. > > Yay, glad that was it. I appreciate that you are trying these out. > > =46TR, the prerelease tarball Stephen make creates Emacs 28.3. That's > slightly different from what I think of as normal but might work to > our advantage. > > The only part of the file names I thought about, particularly, was > deciding to append =22-rc1=22 to the base names for this set. The base > names are generally derived from how Emacs built from the tarball > self-identifies. In particular, =22nsi=22 script (which creates the > self-installer) is fairly fussy about how we name the folder > containing Emacs as produced by =22make install=22; I'd have had variou= s > stuff to figure out I'd wanted to publish this as 28.2.90 (even > assuming I'm correct that would have been a more typical version > identifier for prerelease we're discussing, which I'm not quite ready > to). > > Usually, the pre-release tarballs I've worked with create Emacs > versioned as X.Y.Z, with =22X=22 being the relevant major version, =22Y= =22 > being the last stable minor version of that major version (or zero if, > e.g. the prerelease will become X.1), and =22Z=22 being 90 + (count of > prior pre-release tarballs published). > > In any case, even if I have *that* hopelessly (or quite trivally) > wrong, even aside how the Windows binaries are named, I think there > may be a practical upshot: > > Stephen and I can potentially republish the same tarballs to the other > site to release Emacs 28.3, effectively turning the pre-release into > the release. > > Do we agree that would work=3F And that we are ready=3F Are there > ancillary changes, such as updating online manuals=5B0=5D=3F > > Eli=3F > > =5B0=5D https://www.gnu.org/software/emacs/manual/ --6421c078_2cd89a32_2a3 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Who needs to sign off to do the release=3F Is that = only Eli or Stefan=3F
On Mar 18, 2023 at 3:08 PM -0600, C= orwin Brust <corwin=40bru.st>, wrote:
On Sat, Mar 18, 2023 at 2:30=E2=80=AFPM Drew Adams <drew.ada= ms=40oracle.com> wrote:

The latest RC I see at https://urldefense.c= om/v3/=5F=5Fhttps://alpha.gnu.org/gnu/emacs/pretest/windows/emacs-28
is RC1, dated 2023-02-19.

=5Bsnip=5D

Duh. =46or some reason I was seeing the =22rc1=22 in the name
and not noticing the =2228.3=22 in the name. Thx.

Yay, glad that was it. I appreciate that you are trying these out.

=46TR, the prerelease tarball Stephen make creates Emacs 28.3. That's
slightly different from what I think of as normal but might work to
= our advantage.

The only part of the file names I thought about, particularly, was
deciding to append =22-rc1=22 to the base names for this set. The base names are generally derived from how Emacs built from the tarball
self-identifies. In particular, =22nsi=22 script (which creates the
= self-installer) is fairly fussy about how we name the folder
containing Emacs as produced by =22make install=22; I'd have had various<= br /> stuff to figure out I'd wanted to publish this as 28.2.90 (even
assuming I'm correct that would have been a more typical version
identifier for prerelease we're discussing, which I'm not quite ready
to).

Usually, the pre-release tarballs I've worked with create Emacs
versioned as X.Y.Z, with =22X=22 being the relevant major version, =22Y=22=
being the last stable minor version of that major version (or zero if, e.g. the prerelease will become X.1), and =22Z=22 being 90 + (count of prior pre-release tarballs published).

In any case, even if I have *that* hopelessly (or quite trivally)
wrong, even aside how the Windows binaries are named, I think there
= may be a practical upshot:

Stephen and I can potentially republish the same tarballs to the other site to release Emacs 28.3, effectively turning the pre-release into
the release.

Do we agree that would work=3F And that we are ready=3F Are there
ancillary changes, such as updating online manuals=5B0=5D=3F

Eli=3F

=5B0=5D https://www.gnu.org/software/emacs/manual/
--6421c078_2cd89a32_2a3--