emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: emacs-orgmode@gnu.org
Subject: Re: An experimental way to track Org confirmed bugs, upcoming changes and releases
Date: Mon, 01 Jun 2020 17:30:32 +0200	[thread overview]
Message-ID: <87ftbe2487.fsf@gnu.org> (raw)
In-Reply-To: <87y2p64xo7.fsf@gnu.org> (Bastien's message of "Mon, 01 Jun 2020 17:23:52 +0200")

Bastien <bzg@gnu.org> writes:

> I've developed an experimental tool to help everyone track confirmed
> bugs, upcoming changes and releases

Here is what contributors/maintainers need to know:

To confirm a bug, reply to the bug report and add:

  X-Woof-Bug: confirmed

To mark a bug as "fixed", reply in the same thread and add:

  X-Woof-Bug: fixed

To announce a change, use this:

  X-Woof-Change: commithash orgversion

where commithash corresponds to the commit where the change is
implemented and orgversion to the version where it is released.

To announce a release, use this:

  X-Woof-Release: orgversion

The rules are pretty basic:

- anyone on the list can confirm a bug;
- anyone can announce a change;
- only the maintainer can announce a release.


      reply	other threads:[~2020-06-01 15:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-01 15:23 An experimental way to track Org confirmed bugs, upcoming changes and releases Bastien
2020-06-01 15:30 ` Bastien [this message]

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87ftbe2487.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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 public inbox


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).