From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: New Package for NonGNU-ELPA: clojure-ts-mode Date: Thu, 31 Aug 2023 13:51:08 +0300 Message-ID: <83bkeneb8j.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <87o7j99304.fsf@dfreeman.email> <87wmxj27fn.fsf@dfreeman.email> <831qfrptiq.fsf@gnu.org> <57429221-d9be-5791-e975-b3539905e2f6@gutov.dev> <83a5udlj47.fsf@gnu.org> <87a5udk1co.fsf@posteo.net> <835y51kslv.fsf@gnu.org> <7a82c524-1aa1-e755-e377-673ebb107a44@gutov.dev> <83r0nok8s4.fsf@gnu.org> <87il90znco.fsf@yahoo.com> <1977fbef-307b-bcf4-9448-64f26916dd65@gutov.dev> <87edjozlqq.fsf@yahoo.com> <43ddad10-49dd-1c49-ebfe-51689780b315@gutov.dev> <83jztgk410.fsf@gnu.org> <83edjojx8c.fsf@gnu.org> <8734zzv7vk.fsf@localhost> <83edjjecmx.fsf@gnu.org> <87wmxbtsd4.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26653"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, dmitry@gutov.dev, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 31 12:52:30 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 1qbfHp-0006iL-Fb for ged-emacs-devel@m.gmane-mx.org; Thu, 31 Aug 2023 12:52:29 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbfGy-0007A2-3K; Thu, 31 Aug 2023 06:51:37 -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 1qbfGp-00079R-Gc for emacs-devel@gnu.org; Thu, 31 Aug 2023 06:51:27 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbfGo-0005KL-Gu; Thu, 31 Aug 2023 06:51:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=GZeA/TMcYoAmZxtQ6H08hZUK6cjl1ESRkOA0spn503Q=; b=BmOZ6GAmZyEs B0hMcvjavlpse1zhfymTNghaxfV7s6bG7R2OpIsV3y1Ipxdo6/3ApzDASgxloUEjZPs3Alk4YP9wn D46RVJEidlWuMZXBe6ZfMO6AWKIwpsu+8Bkk/rw+f/klCtLKk95YZtvQK4XqkSdMDfslkGXVh19xF 300IU6VuiMU0NDEzj+ylp9d0Q917NX1Vtqn1fCmSXUCKP06u9n3o58gFULPWzU7fbzeux6AXOEN1J ln6FnOJ1SMqf0xrSjxdBfm9pptiJb0szpsSqOFIwYUIxfOIcblmaozcj72WbEsBJDG9zAyIWu8WYB vRuMoqtPusQDNU8VVmzXpQ==; In-Reply-To: <87wmxbtsd4.fsf@localhost> (message from Ihor Radchenko on Thu, 31 Aug 2023 10:32:07 +0000) 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:309619 Archived-At: > From: Ihor Radchenko > Cc: stefankangas@gmail.com, dmitry@gutov.dev, emacs-devel@gnu.org > Date: Thu, 31 Aug 2023 10:32:07 +0000 > > Eli Zaretskii writes: > > >> Is there any downside holding on a minor release if _some_ bugs are > >> already fixed, even if others are not yet? > > > > What would be the point? People who want something like that can > > simply build the Git release branch, where we fix bugs every few days. > > For Org, a number of people just update from ELPA. Releasing benefits > these users. I don't see how is that different from updating from Git. > > A minor release is more than just code with some bugs fixed: it (a) > > has no known bugs except those whose fix is too risky, and (b) was > > tested in the wild during a pretest. > > You are right. To clarify: I am talking about _bugfix_ releases. Like > Org 9.6.7 -> 9.6.8. Emacs does not have those, currently. If bugfix releases just fix bugs, then basically every commit on the release branch is such a "release", because we only fix bugs there. And don't forget that minor releases affect downstream distros: they need to package a new release, patch it, announce it, manage it, etc. It's very different from a single package, even a package that is as large as Org. > >> What I recently did for Org's bugfix releases was: > >> 1. Every two weeks I see if some bug fixes landed on bugfix branch > >> 2. If there are, I just tag a bugfix release > > > > If all you do is tag a commit, then that's not what constitutes a > > minor release in Emacs. We do much more than just tagging. > > So, what about "bugfix" releases? AFAIU, it is mostly producing a > release tarball + waiting for Emacs to be packaged on major GNU/Linux > distributions. The timing would be anything acceptable for the latter > task, which appears to be a bottleneck in such scenario. That has only disadvantages from my POV: 2 hours of work to produce and test a tarball with no benefits at all. If someone wants to volunteer to do that, fine. (But then making a tarball by following the instructions in make-tarball.txt is easy, and anyone can do that for themselves if they want to.)