From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: Org-mode bugs in the Emacs bug tracker Date: Sat, 12 Dec 2020 12:46:42 +1100 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: multipart/alternative; boundary="0000000000005961c705b63a95c9" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8040"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Stefan Kangas , Boruch Baum , Emacs-Devel List To: Bastien Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 12 02:49:45 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 1knu2b-00020r-DJ for ged-emacs-devel@m.gmane-mx.org; Sat, 12 Dec 2020 02:49:45 +0100 Original-Received: from localhost ([::1]:50998 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1knu2a-0003WX-Eu for ged-emacs-devel@m.gmane-mx.org; Fri, 11 Dec 2020 20:49:44 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57480) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kntzy-0002tS-74 for emacs-devel@gnu.org; Fri, 11 Dec 2020 20:47:02 -0500 Original-Received: from mail-ot1-x334.google.com ([2607:f8b0:4864:20::334]:33250) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kntzr-000832-EM; Fri, 11 Dec 2020 20:47:00 -0500 Original-Received: by mail-ot1-x334.google.com with SMTP id b18so10073520ots.0; Fri, 11 Dec 2020 17:46:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uVOl6sjWF03iCU4k372wILS1VK6qezA3ccuF6RqDk7w=; b=SO6Zyik5iSHZ48IZph4rqi0rqtutj+fP2oXs7CX8tnW1jrrpGMqoOfM8tPAf9MMQNR LXFDfw+ZCc6KwNRsnJed3qgDcitvLl2EVL1up4pUjEra2VLgNiPMD+vJn4Ez9rgmaz09 tKrYw2qd9+uYTMISbKGqXE1bRmn8hPapFvPf7QGl/iJEh7C4SlgD/69nK8d+uK6XP6ac wNnOa7duH7GFtJ1LG4jJR54cTJ4BewsPndfgodUwV+hW+SDmltg2RWYfHgJeYmqueasE Ezr/I6Xc6y0ll61GSY8vwHuCRhjaIifQn67QnUW7O8CCdAsFwGUJK9rgGS1XJEGxul3y dQKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uVOl6sjWF03iCU4k372wILS1VK6qezA3ccuF6RqDk7w=; b=Lt2cjyzvbE7imxDMTeoDOw5X6mJ7bt2kvEKNuarg7HP/SBkIm3KcVdDE2+ZmKoKk19 QxXT3IPLwVohvkwmIInBicDN9c9j7zf1NDOGJmwpqLEkYyAb9qKDCSYtJTbJLR/kh546 uMGF2AVtDXSsH/pQ2AT3nHQbmJg0xko0djVuc66cF9iguTda6jvzllAP3nbmToltndBW 7BnYA3O4vhxGbO/fI0zEpi35Kr8DGB1bANlaNKXfSQM8jBKe8tIJbFQmO83A9n1Dugi7 U2g9RjHeI31Hat9KrrbVKRkjtkvy8HhTIRdBejxaztIAYaObqTI6wqWEeMkcmMVnom8H wgYQ== X-Gm-Message-State: AOAM532GJf+TXrDoF08JH4TPodIAEe+ET2Jk430xeFgy2lxX9jkChegR btk5RSolg7VeR3OqIGhzP9y4Gu85qdB9d+yZiTi2S03DlHQ= X-Google-Smtp-Source: ABdhPJw7ofDonnX6mGuqsx/b60XCmq3EurNcUu/nACbyTjowMMFMzLBkqUeCnnYHcsJXoLIH3mfxoklQmee2k6zWR3s= X-Received: by 2002:a05:6830:1649:: with SMTP id h9mr11738760otr.235.1607737613573; Fri, 11 Dec 2020 17:46:53 -0800 (PST) In-Reply-To: <87im97ew7g.fsf@bzg.fr> Received-SPF: pass client-ip=2607:f8b0:4864:20::334; envelope-from=theophilusx@gmail.com; helo=mail-ot1-x334.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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:260704 Archived-At: --0000000000005961c705b63a95c9 Content-Type: text/plain; charset="UTF-8" Thanks Bastien. Seeing that updates.orgmode.org is now working really helps. On Sat, 12 Dec 2020 at 10:53, Bastien wrote: > Hi Tim, > > Tim Cross 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, > > -- > Bastien > -- regards, Tim -- Tim Cross --0000000000005961c705b63a95c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks Bastien. Seeing that updates.orgmode.org is now working really helps.

On Sat, 12 Dec= 2020 at 10:53, Bastien <bzg@gnu.org&= gt; wrote:
Hi Ti= m,

Tim Cross <th= eophilusx@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-orgmo= de@gnu.org get tracked

For years, M-x org-submit-bug-report sends reports to this list, and
the list *is* the bug tracker.=C2=A0 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).=C2=A0

Your safest bet is to check bugs on updates because bugs there have
been *confirmed* by someone.=C2=A0 Clicking on a bug on updates.orgmode.or= g
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.cg= i?package=3Dorg-mode
https://debbugs.gnu.org/cgi/pkgreport.cgi= ?package=3Demacs

Sometimes bugs reports on debbugs are also shared on this list.

> 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 a= nd
> 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).=C2=A0

You can go on https://updates.orgmode.org

You will find bugs to work on and requests for help.

Best,

--
=C2=A0Bastien


--
regards,

Tim

--
Tim Cross

--0000000000005961c705b63a95c9--