From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Org-mode bugs in the Emacs bug tracker Date: Sat, 12 Dec 2020 05:11:46 +0000 Message-ID: References: <20201206092641.xv5gkqcwbpc5gau7@E15-2016.optimum.net> <87o8j1537q.fsf@bzg.fr> <87pn3g52gg.fsf@bzg.fr> <87im97ew7g.fsf@bzg.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23315"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Kangas , Boruch Baum , Emacs-Devel List To: emacs-devel@gnu.org, Bastien , Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 12 06:13:14 2020 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 1knxDV-0005y9-60 for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Dec 2020 06:13:13 +0100 Original-Received: from localhost ([::1]:52034 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knxDU-0008Dc-6s for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Dec 2020 00:13:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:33848) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knxCL-0007kd-6L for emacs-devel@gnu.org; Sat, 12 Dec 2020 00:12:01 -0500 Original-Received: from stw1.rcdrun.com ([217.170.207.13]:35307) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1knxCH-0006PD-Va; Sat, 12 Dec 2020 00:11:59 -0500 Original-Received: from [192.168.43.201] ([::ffff:41.202.241.42]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_CHACHA20_POLY1305) by stw1.rcdrun.com with ESMTPSA id 00000000002935DC.000000005FD45119.00000F17; Fri, 11 Dec 2020 22:11:53 -0700 In-Reply-To: <87im97ew7g.fsf@bzg.fr> Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:260705 Archived-At: 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 b= us nor references=2E You need summary it on a WWW page and include a hyperl= ink in the but report template=2E Am December 11, 2020 11:53:23 PM UTC schrieb Bastien : >Hi Tim, > >Tim Cross writes: > >> What is https://updates=2Eorgmode=2Eorg?=20 > >See the announcement on this list: >https://orgmode=2Eorg/list/87y2p6ltlg=2Efsf@bzg=2Efr/ > >It is a way to track important updates: mainly confirmed bugs, >upcoming changes, help requests, patches, latest releases=2E > >> when I try that url, I get a 502 bad gateway error=2E > >Fixed, thanks=2E > >> The bit I find frustrating is I don't know where bug submitted to=20 >> emacs-orgmode@gnu=2Eorg get tracked=20 > >For years, M-x org-submit-bug-report sends reports to this list, and >the list *is* the bug tracker=2E I=2Ee=2E we had no bug tracker=2E > >Some users use M-x report-emacs-bugs to submit Org bugs, these bugs >get tracked on debbugs=2E > >> i=2Ee=2E those which are only submitted >> to the list and are not passed to the list from debbugs=2Egnu=2Eorg=2E = 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=2E I don't mind if this means checking >> multiple repositories (though it would be better if there was one >> definitive repository)=2E=C2=A0 > >Your safest bet is to check bugs on updates because bugs there have >been *confirmed* by someone=2E Clicking on a bug on updates=2Eorgmode=2E= org >will bring you to the conversation on this list where the bug have >been confirmed=2E > >Then, you can track bugs from debbugs, using one of these URLs: > >https://debbugs=2Egnu=2Eorg/cgi/pkgreport=2Ecgi?package=3Dorg-mode >https://debbugs=2Egnu=2Eorg/cgi/pkgreport=2Ecgi?package=3Demacs > >Sometimes bugs reports on debbugs are also shared on this list=2E > >> Is there some place where all bugs reported to emacs-orgmode=C2=A0list = are >> tracked? For example, if tomorrow I find I have=C2=A0some spare time an= d >> 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)=2E=C2=A0 > >You can go on https://updates=2Eorgmode=2Eorg > >You will find bugs to work on and requests for help=2E > >Best,