From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Wed, 18 Nov 2015 21:19:23 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: <878u5upw7o.fsf@lifelogs.com> References: <83k2ptq5t3.fsf@gnu.org> <87h9kxx60e.fsf@lifelogs.com> <877flswse5.fsf@lifelogs.com> <8737wgw7kf.fsf@lifelogs.com> <87io5bv1it.fsf@lifelogs.com> <87egfzuwca.fsf@lifelogs.com> <876118u6f2.fsf@lifelogs.com> <8737w3qero.fsf@lifelogs.com> <831tbn9g9j.fsf@gnu.org> Reply-To: emacs-devel@gnu.org NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1447899588 25097 80.91.229.3 (19 Nov 2015 02:19:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Nov 2015 02:19:48 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 19 03:19:40 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 1ZzEp1-0006XE-Nv for ged-emacs-devel@m.gmane.org; Thu, 19 Nov 2015 03:19:39 +0100 Original-Received: from localhost ([::1]:39201 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzEp1-0007Zx-6h for ged-emacs-devel@m.gmane.org; Wed, 18 Nov 2015 21:19:39 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:40305) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzEox-0007Ze-S1 for emacs-devel@gnu.org; Wed, 18 Nov 2015 21:19:36 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZzEot-0007UA-4N for emacs-devel@gnu.org; Wed, 18 Nov 2015 21:19:35 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:59282) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZzEos-0007Tn-U6 for emacs-devel@gnu.org; Wed, 18 Nov 2015 21:19:31 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZzEor-0006FT-BC for emacs-devel@gnu.org; Thu, 19 Nov 2015 03:19:29 +0100 Original-Received: from 98.229.60.157 ([98.229.60.157]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Nov 2015 03:19:29 +0100 Original-Received: from tzz by 98.229.60.157 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 19 Nov 2015 03:19:29 +0100 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: emacs-devel@gnu.org Original-Lines: 38 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 98.229.60.157 X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" Mail-Copies-To: never User-Agent: Gnus/5.130012 (Ma Gnus v0.12) Emacs/25.0.50 (gnu/linux) Cancel-Lock: sha1:77Ks4xrp3SbJoCdfVrQU4L7O/JE= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:194768 Archived-At: On Wed, 18 Nov 2015 22:58:16 +0200 Eli Zaretskii wrote: >> From: Ted Zlatanov >> Date: Wed, 18 Nov 2015 14:38:35 -0500 >> >> * what planned features remain unfinished? >> * are there any known bugs? EZ> Not for me to answer, but in any case new features should go to EZ> master, I think. Therefore, I suggest to wait with them until what we EZ> have on the release branch stabilizes. (E.g., I just had to make some EZ> fixes there in the Windows-specific code, and also the code is EZ> formatted not according to our conventions.) I agree that new features should go to master. I wanted to find out, for when we write the NEWS entries and other docs, and for general tracking of progress, what deficiencies (unfinished features and bugs) remain. Sorry for letting bad formatting slip through. I checked the code but I guess wasn't thorough. Would you recommend a specific tool for the formatting review? >> * should there be a separate manual or at least a section in the developer manual? EZ> Of course! Every feature should be documented, and this one is no EZ> exception. I suggest to start with NEWS. My goal with that question was actually to find out *where* the developer docs should go, not whether they are necessary. I think we all agree on the necessity. I can try a first stab at them when I know in what context they'll exist. Regarding NEWS specifically, Aurélien is absent at the moment and will be back next week. Maybe Philipp would like to provide the NEWS entries? I will write them if neither of them is able or if it can't wait until next week. Ted