From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jason Rumney Newsgroups: gmane.emacs.devel Subject: Re: Pretest and branch on Friday June 19 Date: Sat, 13 Jun 2009 09:36:56 +0800 Message-ID: <4A3302B8.1050704@gnu.org> References: <87k53h10vx.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1244857106 9944 80.91.229.12 (13 Jun 2009 01:38:26 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 13 Jun 2009 01:38:26 +0000 (UTC) Cc: emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 13 03:38:24 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MFICN-0005SU-PO for ged-emacs-devel@m.gmane.org; Sat, 13 Jun 2009 03:38:24 +0200 Original-Received: from localhost ([127.0.0.1]:49054 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFICN-0001LH-B9 for ged-emacs-devel@m.gmane.org; Fri, 12 Jun 2009 21:38:23 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MFIBc-0000f7-BH for emacs-devel@gnu.org; Fri, 12 Jun 2009 21:37:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MFIBX-0000Zi-CW for emacs-devel@gnu.org; Fri, 12 Jun 2009 21:37:35 -0400 Original-Received: from [199.232.76.173] (port=37121 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFIBX-0000ZX-4M for emacs-devel@gnu.org; Fri, 12 Jun 2009 21:37:31 -0400 Original-Received: from mail-pz0-f203.google.com ([209.85.222.203]:64809) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MFIBW-0001Sv-PO for emacs-devel@gnu.org; Fri, 12 Jun 2009 21:37:30 -0400 Original-Received: by pzk41 with SMTP id 41so1442647pzk.14 for ; Fri, 12 Jun 2009 18:37:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=/lwgdRaEfDwe9EbyNo/QyS0WkyUAJE9ra9eO6QbJ9i0=; b=f1AOVX5yBzb44gLWwx28IcXpt3yIg+nw+Sv0GRYqtKmzZHCwMjGU8GIQys3q5OLw9f mNt/OTrqi+NLNvnu3cgApR72Q5djfZgjYx2tMYAq5aLhyRsEkO+y1NxMl1JTa3PyljeD AZuooZatSxyY/dUD6jN2r/7SmBLhuExKtr8hc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=MoecHKrUEHiKEuxZwu/dLUpLFLSHkI2+kFMWPyN0luC/qoKNdxbbpg1UUTegxuqkhb k06ONPQzk3UfCXk3D2fewDEozxF0RqYmJuNHgcSqppTAWdD31bIKkES1WXibvCdZ1ssi k7gxMVtiWSC7xJGPsua5+iuVfM3xE96ADMP5k= Original-Received: by 10.142.169.4 with SMTP id r4mr1556115wfe.262.1244857049059; Fri, 12 Jun 2009 18:37:29 -0700 (PDT) Original-Received: from ?192.168.249.26? ([124.13.2.139]) by mx.google.com with ESMTPS id 20sm2219052wfi.20.2009.06.12.18.37.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Jun 2009 18:37:28 -0700 (PDT) User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) In-Reply-To: <87k53h10vx.fsf@cyd.mit.edu> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:111471 Archived-At: Chong Yidong wrote: > I'm not certain what version number to assign the trunk after branching. > I'm inclined to use 23.1.50, which assumes we'll use the trunk for > developing 23.2. Maybe this is optimistic; as many will recall, what > ended up as Emacs 22 was originally slated for 21.3. Opinions welcome. > I don't think there are major changes like multi-tty or unicode pending, but there are a lot of minor features being held back, so 23.1.50 seems appropriate to me. When someone comes up with a major new feature (collaborative editing, or bidi becoming close to usable), we can develop that on a branch like was done with unicode and multi-tty (hopefully by then we will be using bzr).