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 16:20:38 +0300 Message-ID: <83v8cvcpqx.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <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> <83bkeneb8j.fsf@gnu.org> <87ledrtqzx.fsf@localhost> <837cpbe5vx.fsf@gnu.org> <87ttsfs6yo.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="17288"; 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 15:21:37 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 1qbhc9-0004GS-Eg for ged-emacs-devel@m.gmane-mx.org; Thu, 31 Aug 2023 15:21:37 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbhbY-0006vy-1j; Thu, 31 Aug 2023 09:21:00 -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 1qbhbV-0006qu-Qa for emacs-devel@gnu.org; Thu, 31 Aug 2023 09:20:58 -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 1qbhbV-0005mV-7y; Thu, 31 Aug 2023 09:20:57 -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=BpKm1kTrQjyJdTSrMeLILNt7fvODtBkr34Ah5x27gyY=; b=WBO5oe4I/1bf j9CFzbxzG/Ugt2LRRzg+jGEUk9cIdKBxU5h4+PHD1yMaZFsqd8gJh0BrSPh4e8ZgEGLEl+ErlzpGU B9RMVH3abP0Cuhw5EmJtkWH/LoWsRVFgX6PWd+I2+D+6oHL8Km9mKNx6EwTgJ0pANylHerR4QtBAh Z937tqfg+RkW0Dju/rS2yI55oBemD41yli2poGlEiT5tA7eCKvgJlmuJLLJAhyiIFqeTq1GkjWDOg sZmKCwaHkEJkC2Nj9lnSikvk8u6kvIG6k2FNzypRLEETpD6EQbhZOzLlofge8LmT6POQdsoYYsgTr U5XnHfwOioSw9HZtJoPr8Q==; In-Reply-To: <87ttsfs6yo.fsf@localhost> (message from Ihor Radchenko on Thu, 31 Aug 2023 12:59:43 +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:309658 Archived-At: > From: Ihor Radchenko > Cc: stefankangas@gmail.com, dmitry@gutov.dev, emacs-devel@gnu.org > Date: Thu, 31 Aug 2023 12:59:43 +0000 > > Eli Zaretskii writes: > > >> Not all the users are even familiar with Git. > > > > Are you sure? I'm not. > > > > And we aren't talking about "all the users", only those who want all > > the latest fixes ASAP. Emacs is a large and very stable package, so > > the probability that the latest bugfix affects a particular user is > > very low. Thus, I believe that people who really need frequent > > bugfixes are quite a few. > > I have a particular category of users in mind - the bug reporters > themselves. It would be nice if they had an opportunity to get _their_ > bug fixed simply after soon-ish bugfix update. People who report bugs > are quite often just ordinary users, who do not know anything about > patches or git. That already happens -- we almost always either post the patches or point to the commits (or both). So these users are not the main target audience for the minor releases. > >> > 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.) > >> > >> Can it be simply automated? > > > > Not easily, no. There's always stuff that needs manual intervention. > > Maybe someone could write and maintain a smart enough program to do > > that, but it's not trivial, and there are always new issues to add to > > that. > > I have looked through admin/make-tarball.txt, and I can mostly see hassle > with updating NEWS file. Look closer. NEWS actually don't present a problem that needs to be fixed manually. > Or do you have some other problems in mind? Yes. > (Also, note that Po Lu seems to have some working code to generate tarballs) So do we: see the make-dist script. This is not what takes me two hours each time I need to produce a release tarball. (I actually don't understand where this discussion is going. Do you really believe I'm so ... unwise, after all these years, that I spend two full hours of my time on something that can be easily automated? really??)