From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id oCm/F0Ef1V6zTgAA0tVLHw (envelope-from ) for ; Mon, 01 Jun 2020 15:31:13 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id wLF6E0Ef1V5BUwAAbx9fmQ (envelope-from ) for ; Mon, 01 Jun 2020 15:31:13 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 70F53940AD0 for ; Mon, 1 Jun 2020 15:31:10 +0000 (UTC) Received: from localhost ([::1]:45348 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jfmP3-0003LB-Tq for larch@yhetil.org; Mon, 01 Jun 2020 11:31:06 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:45534) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jfmOZ-0003Kk-K0 for emacs-orgmode@gnu.org; Mon, 01 Jun 2020 11:30:35 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:51026) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jfmOZ-0001UU-B0 for emacs-orgmode@gnu.org; Mon, 01 Jun 2020 11:30:35 -0400 Received: from lns-bzn-32-82-254-31-120.adsl.proxad.net ([82.254.31.120]:48276 helo=guerry) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) (envelope-from ) id 1jfmOY-0000GQ-KS for emacs-orgmode@gnu.org; Mon, 01 Jun 2020 11:30:34 -0400 Received: by guerry (Postfix, from userid 1000) id 7706C1A603C1; Mon, 1 Jun 2020 17:30:32 +0200 (CEST) From: Bastien To: emacs-orgmode@gnu.org Subject: Re: An experimental way to track Org confirmed bugs, upcoming changes and releases Organization: GNU References: <87y2p64xo7.fsf@gnu.org> Date: Mon, 01 Jun 2020 17:30:32 +0200 In-Reply-To: <87y2p64xo7.fsf@gnu.org> (Bastien's message of "Mon, 01 Jun 2020 17:23:52 +0200") Message-ID: <87ftbe2487.fsf@gnu.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.01 X-TUID: kXmcRqZ9zYJ3 Bastien 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