An experimental way to track Org confirmed bugs, upcoming changes and releases

An experimental way to track Org confirmed bugs, upcoming changes and releases

[Bastien]

Hi all,

I've developed an experimental tool to help everyone track confirmed
bugs, upcoming changes and releases and I've set it up for Org here:

https://updates.orgmode.org

It is based on this piece of software: https://github.com/bzg/woof

You can subscribe to all Org updates through this feed:
https://updates.orgmode.org/feed/updates

Or just subscribe to confirmed bugs, upcoming changes and releases:

https://updates.orgmode.org/feed/bugs
https://updates.orgmode.org/feed/changes
https://updates.orgmode.org/feed/releases

This is *not* a bug tracking tool.

It is a way to better communicate what happens on this mailing list.

The mailing list is our preferred way to communicate for any request:
asking for help, sharing an article, reporting a bug or submitting a
patch.  It has been for years - and I hope it will continue for more
years, because I feel it encourages respect, thoughtful discussions
and an efficient way to help each others.

The tool is experimental: if it proves useful, let's try to keep it,
otherwise let's drop it: our main focus should be in recruiting new
developers to help with the codebase.

Thanks,

-- 
 Bastien

Re: An experimental way to track Org confirmed bugs, upcoming changes and releases

[Bastien]

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.

-- 
 Bastien