From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7275 invoked by alias); 25 Jun 2019 00:05:27 -0000 Mailing-List: contact bzip2-devel-help@sourceware.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Subscribe: List-Id: Sender: bzip2-devel-owner@sourceware.org Received: (qmail 7263 invoked by uid 89); 25 Jun 2019 00:05:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.100.3 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=ultra, efforts X-Spam-Status: No, score=-6.6 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on sourceware.org X-Spam-Level: X-HELO: gnu.wildebeest.org Message-ID: Subject: Releasing bzip2 1.0.7 and 1.1.0 ? Was: [PATCH] bzip2: Fix return value when combining --test,-t and -q. From: Mark Wielaard To: Santiago Ruano =?ISO-8859-1?Q?Rinc=F3n?= Cc: bzip2-devel@sourceware.org, Anibal Monsalve Salazar , Anthony Fok , Federico Mena Quintero Date: Tue, 01 Jan 2019 00:00:00 -0000 In-Reply-To: References: <1561362056-4393-1-git-send-email-mark@klomp.org> <20190624083116.GN6125@bartik> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Evolution 3.28.5 (3.28.5-2.el7) Mime-Version: 1.0 X-Spam-Flag: NO X-SW-Source: 2019-q2/txt/msg00008.txt.bz2 Hi, On Mon, 2019-06-24 at 11:34 +0200, Mark Wielaard wrote: > So I was thinking, first do a new 1.0.7 release with just the distro > fixes and the updated project home, and then look at updating the > rest of the build infrastructure. I have been pondering what to do about the duplicate efforts to get a bzip2 1.0.7 release out. I am really conservative and really think it would be good to do a release as is from the sourceware.org bzip2.git with just the security/bug fixes. And I think it would not be good to force the SO_NAME issue by updating the build system simultaneously. I am also reluctant to include the "e" and/or O_CLOEXEC fix as is, because a) not all distros have it currently (or different variants of it) and b) it might not exist on all platforms, so would need some kind of check for that first. On the other hand, I do actually think it would be good to have a more modern build system, and to force the SO_NAME issue (although I think we should provide upstream support for changing it back to libbz2.so.1.0 for those people who have been using it and don't want to break backward compatibility). And using newer, more modern, possibly GNU/Linux only features in 2019 would be a good thing. So what about we do a conservative release of 1.0.7 from the current sourceware.org bzip2.git and simultaneously do a 1.1.0 release from the gitlab hosted git repo? Referencing each other as the "classic" and "modern" bzip2 versions. Then we can keep the sourceware.org bzip2.git around for ultra conservative releases based on the current build "system" (that basically only takes new security issues), using 1.0.8, 1.0.9, etc. But encourage people towards the 1.1.1, 1.1.2, etc. releases for a more modern experience, if at all possible. Cheers, Mark