unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Stephen Leake <stephen_leake@stephe-leake.org>,
	emacs-tangents@gnu.org, Richard Stallman <rms@gnu.org>,
	john@yates-sheets.org
Subject: Re: Too few people taking care of bug reports,
Date: Wed, 11 Nov 2015 13:06:37 -0800	[thread overview]
Message-ID: <m2fv0cdz4y.fsf@Vulcan.attlocal.net> (raw)
In-Reply-To: <5643AD34.3000803@yandex.ru> (Dmitry Gutov's message of "Wed, 11 Nov 2015 23:03:48 +0200")

>>>>> Dmitry Gutov <dgutov@yandex.ru> writes:

> Still, though, the bug reports for ELPA packages that don't have any other
> upstream are supposed to go into the Emacs bug tracker anyway.

> It's not like upon moving a package to ELPA, we can immediately declare it
> obsolete. Right?

This is true. At least it will get a tag so that we know it's in ELPA. ELPA
packages have the advantage of being able to deliver bug fixes post-release
very easily. Anything that's in core has a much longer delay, and so is more
important to fix sooner for that reason.

John



  reply	other threads:[~2015-11-11 21:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJnXXogfOJEO3fbiVnE-v3q_KAM71wO_YUw7NBehwTE4S1SMsQ@mail.gmail.com>
     [not found] ` <m2611ahqtq.fsf@Vulcan.attlocal.net>
     [not found]   ` <8337wdn6uu.fsf@gnu.org>
     [not found]     ` <m26119bxcj.fsf@Vulcan.attlocal.net>
     [not found]       ` <86611975jo.fsf_-_@stephe-leake.org>
     [not found]         ` <838u65kxly.fsf@gnu.org>
     [not found]           ` <86mvuk4xxd.fsf@stephe-leake.org>
     [not found]             ` <831tbwlext.fsf@gnu.org>
2015-11-11 20:39               ` Too few people taking care of bug reports, was: Re: Release process (was Re: Move to a cadence release model?) Dmitry Gutov
2015-11-11 20:50                 ` Too few people taking care of bug reports, John Wiegley
2015-11-11 21:03                   ` Dmitry Gutov
2015-11-11 21:06                     ` John Wiegley [this message]
2015-11-11 21:14                   ` Eli Zaretskii
2015-11-11 21:10                 ` Too few people taking care of bug reports, was: Re: Release process (was Re: Move to a cadence release model?) Eli Zaretskii
2015-11-11 21:15                   ` Too few people taking care of bug reports, John Wiegley
2015-11-11 21:27                     ` Eli Zaretskii
2015-11-11 21:23                   ` Too few people taking care of bug reports, was: Re: Release process (was Re: Move to a cadence release model?) Dmitry Gutov
2015-11-11 21:30                     ` Eli Zaretskii
2015-11-11 21:31                       ` Dmitry Gutov
2015-11-11 21:42                     ` Eli Zaretskii
2015-11-11 21:54                       ` Dmitry Gutov

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m2fv0cdz4y.fsf@Vulcan.attlocal.net \
    --to=jwiegley@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=eliz@gnu.org \
    --cc=emacs-tangents@gnu.org \
    --cc=john@yates-sheets.org \
    --cc=rms@gnu.org \
    --cc=stephen_leake@stephe-leake.org \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).