From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: Feature freezes and Emacs 25 Date: Wed, 18 Nov 2015 14:06:43 -0800 Message-ID: References: <871tc315y3.fsf@lifelogs.com> <83k2pvqg0l.fsf@gnu.org> <837fluqkd1.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1447884558 32686 80.91.229.3 (18 Nov 2015 22:09:18 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 18 Nov 2015 22:09:18 +0000 (UTC) Cc: Xue Fuqiao , Eli Zaretskii , nicolas@petton.fr, Emacs-devel To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 18 23:09:17 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZzAug-0005a7-Qj for ged-emacs-devel@m.gmane.org; Wed, 18 Nov 2015 23:09:14 +0100 Original-Received: from localhost ([::1]:38581 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzAuf-0000tJ-Lx for ged-emacs-devel@m.gmane.org; Wed, 18 Nov 2015 17:09:13 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34601) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzAuR-0000sG-MK for emacs-devel@gnu.org; Wed, 18 Nov 2015 17:09:00 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzAuQ-0003EP-Qm for emacs-devel@gnu.org; Wed, 18 Nov 2015 17:08:59 -0500 Original-Received: from mail-pa0-x235.google.com ([2607:f8b0:400e:c03::235]:35394) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzAuM-00038B-Rg; Wed, 18 Nov 2015 17:08:54 -0500 Original-Received: by pacej9 with SMTP id ej9so57611914pac.2; Wed, 18 Nov 2015 14:08:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:mail-followup-to:mime-version:content-type; bh=P0ZIzajUOSbUSqkZ3gjDglXR7GNj/gkCwZyRqBicDeM=; b=zw76MCwt81x/5E1g3YBfZ0FRR6HnKry7pSHVmoVer/ZpUX+3AfqMDJsN7U8ZG+pHvu psv15l3KI7gi5Mm2FT34I6l3VibWnrG7OLZxs9smWHermmRVzytMdTfiNz6yGZMotFH5 6bhi5nO7y/bqmnrKZ5cE0zY8tMNceWOSukMFgnZS4XXwZ1P4cs6Tou4zlkKV1LXD4xbj oUQy5VgHjDqtprspOBQARsnbLd7UE6Gs4o9fBpYf0TEwn92N4yKnX9fbrMPEmieROruW oQs/fUWtdbdStBC0ahis5M3NmkzdbKfvaOD+NTAiSzPeEIi7pMWDTDI4zWVLewAL9N5n xKcg== X-Received: by 10.66.221.105 with SMTP id qd9mr5487019pac.46.1447884534215; Wed, 18 Nov 2015 14:08:54 -0800 (PST) Original-Received: from Vulcan.local (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id sg4sm6128572pac.48.2015.11.18.14.08.53 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 18 Nov 2015 14:08:53 -0800 (PST) X-Google-Original-From: "John Wiegley" Original-Received: by Vulcan.local (Postfix, from userid 501) id 99B60109DD86A; Wed, 18 Nov 2015 14:08:52 -0800 (PST) In-Reply-To: (Glenn Morris's message of "Wed, 18 Nov 2015 13:12:58 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (darwin) Mail-Followup-To: Glenn Morris , Xue Fuqiao , Eli Zaretskii , nicolas@petton.fr, Emacs-devel X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::235 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:194758 Archived-At: >>>>> Glenn Morris writes: > [I see you use Mail-Followup-To, which results in looking like I'm > writing to someone else.] What is the proper method to use? > You can use a usertag if you prefer, but personally I think block/unblock is > better. Ok, block/unblock sounds fine. > IMO now is the time to start tracking 25.2 (or whatever master is to be > released as) issues as well. The "list of issues that need to be fixed > before release" should always be being updated, else it's easy for items to > get lost. Agreed. John