From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Adrian Robert Newsgroups: gmane.emacs.devel Subject: Release timelines and Unicode2 branch Date: Mon, 12 Sep 2005 14:43:58 -0400 Message-ID: <62DD76A1-D1A5-4B7B-A9C0-6E95A3D09F52@cogsci.ucsd.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1126550912 28662 80.91.229.2 (12 Sep 2005 18:48:32 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 12 Sep 2005 18:48:32 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 12 20:48:29 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EEtK6-0008JD-Hu for ged-emacs-devel@m.gmane.org; Mon, 12 Sep 2005 20:46:34 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EEtK5-0007P9-Vi for ged-emacs-devel@m.gmane.org; Mon, 12 Sep 2005 14:46:33 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EEtJk-0007Fs-Jd for emacs-devel@gnu.org; Mon, 12 Sep 2005 14:46:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EEtJi-0007Dj-KP for emacs-devel@gnu.org; Mon, 12 Sep 2005 14:46:12 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EEtJi-0007DR-Ek for emacs-devel@gnu.org; Mon, 12 Sep 2005 14:46:10 -0400 Original-Received: from [140.251.1.25] (helo=smtp-in1.med.cornell.edu) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1EEtIf-000068-MD for emacs-devel@gnu.org; Mon, 12 Sep 2005 14:45:05 -0400 Original-Received: from mpx2.med.cornell.edu (pc113142-10.med.cornell.edu [140.251.11.119]) by smtp-in1.med.cornell.edu (Switch-3.1.6/Switch-3.1.6) with ESMTP id j8CIhxn5160198 for ; Mon, 12 Sep 2005 14:44:00 -0400 Original-Received: from [140.251.33.115] by mpx2.med.cornell.edu (Sun Java System Messaging Server 6.1 HotFix 0.11 (built Jan 28 2005)) with ESMTP id <0IMP00607W1B9UC0@mpx2.med.cornell.edu> for emacs-devel@gnu.org; Mon, 12 Sep 2005 14:43:59 -0400 (EDT) Original-To: emacs-devel@gnu.org X-Mailer: Apple Mail (2.734) X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.1.0.0, Antispam-Data: 2005.9.12.21 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:42855 Archived-At: Hi, I'm maintaining the Emacs-on-Aqua GNUstep / OS X port, currently based on emacs 20.7 (http://emacs-on-aqua.sf.net/). I want to update this to a more recent version but would ideally like to do so against a stabilized / released version of GNU emacs -- just so I know that bugs are my own fault when doing the port. On the other hand, I'm not sure if the 21.3/21.4 release is best for this since there was a lot of change since then. That brings my first question: 1) When is the best estimate of when 22.1 will come out? My second question concerns the unicode-2 branch of CVS. As I understand it, this branch contains reworked internal handling of character encoding, is receiving updates from CVS Head, and will eventually form the basis for a future emacs release. (23?) To avoid having to rework Emacs-on-Aqua's character handling in the future, I was thinking to base my port on this branch rather than 22.1. So my questions here: 2) Is 22.1 being released off its own branch (instead of the head), and if so are the stabilizations (to be) done there merged into unicode-2? 3) How much significant unicode-2-specific work remains before that branch becomes eligible for a release of its own? (I see from the list archives there are plans to merge unicode into CVS head, but that doesn't necessarily mean there won't be further heavy development before 23.1.) And how stable / bug-free is unicode-2 right now compared with the will-become-22.1 code? What I'm getting at is, is it reasonable to port Emacs-on-Aqua to this branch now, or should I stick with the to-be-22.1 code, or perhaps just wait before starting anything? thanks, Adrian