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.96) (envelope-from ) id 1wSHVL-0035HE-1P for pgsql-www@arkaria.postgresql.org; Wed, 27 May 2026 16:53:15 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wSHVJ-008npo-15 for pgsql-www@arkaria.postgresql.org; Wed, 27 May 2026 16:53:14 +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.96) (envelope-from ) id 1wSHVJ-008npg-0N for pgsql-www@lists.postgresql.org; Wed, 27 May 2026 16:53:14 +0000 Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wSHVG-00000001isC-2n40 for pgsql-www@lists.postgresql.org; Wed, 27 May 2026 16:53:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org; s=smtpauto.stravinsky; h=X-Debian-User:Content-Type:MIME-Version:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=A/2o92ANY5SK8Vz+ZwcH6lZV9iosqxbmUpc9+lvBAwY=; b=gd+pUpybsr7Hm0OFsuJXkfmt/k D8n+h80gPMzPea9yhpx2pqWymyRug7dRzTIBzpYHBu8CeLL0cjTqRptwEEHeVC2C5pBBYjNYK+Cjz EIBoYHV+p3Ht2DNk9HaKQQG3Jtxvs5yzNWMDuu/sWZMoscfoUhse2VC1skEyt0BT7eJW5MQ5/tr8W t9xirBbHVlDYx8hJ81kVfB8aUdZ6MEovCSBWDbiWLTN7C/INwxM6/Vpc9KMFZsWLA5YstAKWy6/oe IKdBdA0rIuzDBq54fhUueuvHwLiXmLXHBdzJF2B05AaXQYLojCjxYDtPBewqBwMKF38Pvdp8uC226 St8WaNqQ==; Received: from authenticated-user by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.96) (envelope-from ) id 1wSHV9-003Jtx-2N; Wed, 27 May 2026 16:53:04 +0000 Date: Wed, 27 May 2026 18:53:02 +0200 From: Christoph Berg To: PostgreSQL WWW Cc: Peter Eisentraut Subject: Beta1 and extensions Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Debian-User: myon List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk In Vancouver (and before that in Brussels), we were talking about beta releases and what we would expect from extension. Someone (I think it was Peter E) suggested that we add something about that to the release notes. Here is a draft: After the beta1 release (scheduled for June), we suggest that extension authors start working on making sure their extensions work with the upcoming PostgreSQL version. Catalog changes and feature reverts can still happen at that time, but should be rare and we would like to hear from extensions about potential problems as early as possible. Ideally, extensions should be ready by the time of the beta2 release (scheduled for August), so packagers can prepare extension packages to be released along with the final rc and GA releases (September). However, I am not sure where exactly to put that information. The release-XX.sgml files are pretty volatile, and the beta information gets removed for the .0 release. Maybe under https://www.postgresql.org/developer/roadmap/ ? Is there a general description of the development cycle that I have missed? Christoph