all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: "Dmitry Gutov" <dgutov@yandex.ru>,
	emacs-devel@gnu.org,
	"Noam Postavsky" <npostavs@users.sourceforge.net>,
	"João Távora" <joaotavora@gmail.com>
Subject: Re: What to do about unmaintained ELPA packages
Date: Mon, 30 May 2022 15:45:29 +0200	[thread overview]
Message-ID: <87o7zfw2va.fsf@gnus.org> (raw)
In-Reply-To: <871qwb5wxv.fsf@posteo.net> (Philip Kaludercic's message of "Mon,  30 May 2022 06:58:04 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

> Considering the number of issues that have been gathering in the above
> mentioned issue tracker, I find it increasingly difficult to say it is
> "stable".

Seems like a bit more than 10% of issues opened are still open?  That's
not a bad track record -- it's about where we are in the Emacs bug
tracker.  😰

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2022-05-30 13:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-29 21:34 What to do about unmaintained ELPA packages Philip Kaludercic
2022-05-29 21:41 ` Stefan Monnier
2022-05-29 21:54 ` Dmitry Gutov
2022-05-29 23:08   ` Tim Cross
2022-05-30 11:14     ` Akib Azmain Turja
2022-05-30  6:58   ` Philip Kaludercic
2022-05-30 13:45     ` Lars Ingebrigtsen [this message]
2022-05-30 14:46     ` João Távora
2022-05-30 22:51       ` Ergus
2022-05-30 23:04         ` João Távora
2022-05-31 16:42       ` Philip Kaludercic
2022-05-31 22:08         ` João Távora
2022-06-01  5:57           ` Bozhidar Batsov
2022-06-01 22:56             ` Richard Stallman
2022-05-30 22:53 ` Richard Stallman
2022-05-31 10:31   ` Akib Azmain Turja
2022-05-31 12:33     ` Stefan Monnier
2022-05-31 13:39       ` Akib Azmain Turja

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7zfw2va.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=npostavs@users.sourceforge.net \
    --cc=philipk@posteo.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.