From: Jean Louis <bugs@gnu.support>
To: emacs-devel@gnu.org, Bastien <bzg@gnu.org>,
Tim Cross <theophilusx@gmail.com>
Cc: Stefan Kangas <stefan@marxist.se>,
Boruch Baum <boruch_baum@gmx.com>,
Emacs-Devel List <emacs-devel@gnu.org>
Subject: Re: Org-mode bugs in the Emacs bug tracker
Date: Sat, 12 Dec 2020 05:11:46 +0000 [thread overview]
Message-ID: <BBB38814-6B42-4718-A004-C7BDBDC14FA0@gnu.support> (raw)
In-Reply-To: <87im97ew7g.fsf@bzg.fr>
Then include that workflow in the Org bug report template, as people using Org who will report bugs do not necessary read this list neither previous bus nor references. You need summary it on a WWW page and include a hyperlink in the but report template.
Am December 11, 2020 11:53:23 PM UTC schrieb Bastien <bzg@gnu.org>:
>Hi Tim,
>
>Tim Cross <theophilusx@gmail.com> writes:
>
>> What is https://updates.orgmode.org?
>
>See the announcement on this list:
>https://orgmode.org/list/87y2p6ltlg.fsf@bzg.fr/
>
>It is a way to track important updates: mainly confirmed bugs,
>upcoming changes, help requests, patches, latest releases.
>
>> when I try that url, I get a 502 bad gateway error.
>
>Fixed, thanks.
>
>> The bit I find frustrating is I don't know where bug submitted to
>> emacs-orgmode@gnu.org get tracked
>
>For years, M-x org-submit-bug-report sends reports to this list, and
>the list *is* the bug tracker. I.e. we had no bug tracker.
>
>Some users use M-x report-emacs-bugs to submit Org bugs, these bugs
>get tracked on debbugs.
>
>> i.e. those which are only submitted
>> to the list and are not passed to the list from debbugs.gnu.org. I
>> see bug reports come through on the list and I sometimes see patches
>> posted to the list to address a bug, but where can I go to see the
>> status of all currently known bugs and see threads relating to work
>> in resolving the bugs etc. I don't mind if this means checking
>> multiple repositories (though it would be better if there was one
>> definitive repository).
>
>Your safest bet is to check bugs on updates because bugs there have
>been *confirmed* by someone. Clicking on a bug on updates.orgmode.org
>will bring you to the conversation on this list where the bug have
>been confirmed.
>
>Then, you can track bugs from debbugs, using one of these URLs:
>
>https://debbugs.gnu.org/cgi/pkgreport.cgi?package=org-mode
>https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs
>
>Sometimes bugs reports on debbugs are also shared on this list.
>
>> Is there some place where all bugs reported to emacs-orgmode list are
>> tracked? For example, if tomorrow I find I have some spare time and
>> would like to contribute to org mode by seeing if I can fix a bug,
>> where can I go to find a list of bugs with current details about the
>> status (including whether someone else is already working to resolve
>> it).
>
>You can go on https://updates.orgmode.org
>
>You will find bugs to work on and requests for help.
>
>Best,
next prev parent reply other threads:[~2020-12-12 5:11 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 9:26 bug archiving policy Boruch Baum
2020-12-06 9:52 ` Stefan Kangas
2020-12-06 10:14 ` Boruch Baum
2020-12-06 10:24 ` Jean Louis
2020-12-10 11:08 ` Bastien
2020-12-10 11:23 ` Stefan Kangas
2020-12-10 14:21 ` Eli Zaretskii
2020-12-11 5:53 ` Bastien
2020-12-06 10:18 ` Jean Louis
2020-12-10 11:10 ` Bastien
2020-12-10 11:57 ` Jean Louis
2020-12-11 5:58 ` Bastien
2020-12-12 5:40 ` Jean Louis
2020-12-12 13:44 ` Stefan Monnier
2020-12-13 9:48 ` Bastien
2020-12-13 16:00 ` Michael Albinus
2020-12-13 16:30 ` Bastien
2020-12-13 18:00 ` Michael Albinus
2020-12-13 17:09 ` Org-mode in debbugs [was Re: bug archiving policy] Glenn Morris
2020-12-13 17:58 ` Michael Albinus
2020-12-10 11:07 ` bug archiving policy Bastien
2020-12-10 13:45 ` Org-mode bugs in the Emacs bug tracker (was: Re: bug archiving policy) Stefan Kangas
2020-12-11 5:36 ` Org-mode bugs in the Emacs bug tracker Bastien
2020-12-11 13:11 ` Stefan Kangas
2020-12-11 21:47 ` Tim Cross
2020-12-11 23:53 ` Bastien
2020-12-12 1:46 ` Tim Cross
2020-12-12 5:11 ` Jean Louis [this message]
2020-12-13 9:41 ` Bastien
2020-12-11 23:45 ` Bastien
2020-12-12 5:42 ` Jean Louis
2020-12-06 9:56 ` bug archiving policy Eli Zaretskii
2020-12-06 10:18 ` Boruch Baum
2020-12-06 10:24 ` Eli Zaretskii
2020-12-06 10:39 ` Boruch Baum
2020-12-06 10:57 ` Eli Zaretskii
2020-12-06 11:13 ` Boruch Baum
2020-12-06 11:22 ` Michael Albinus
2020-12-06 11:28 ` Boruch Baum
2020-12-06 10:21 ` Boruch Baum
2020-12-06 10:52 ` Eli Zaretskii
2020-12-06 11:09 ` Stefan Kangas
2020-12-06 11:18 ` Boruch Baum
2020-12-06 11:25 ` Michael Albinus
2020-12-06 11:30 ` Boruch Baum
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=BBB38814-6B42-4718-A004-C7BDBDC14FA0@gnu.support \
--to=bugs@gnu.support \
--cc=boruch_baum@gmx.com \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
--cc=theophilusx@gmail.com \
/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.