From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Stephen J. Turnbull" Newsgroups: gmane.emacs.devel,gmane.emacs.orgmode Subject: Re: org-export raises stringp nil error Date: Fri, 08 Mar 2013 17:27:56 +0900 Message-ID: <871ubqi9df.fsf@uwakimon.sk.tsukuba.ac.jp> References: <87ip539io1.fsf@nautilus.nautilus> <87zjye96ph.fsf@bzg.ath.cx> <87vc928kcm.fsf@bzg.ath.cx> <513997AD.5050901@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Trace: ger.gmane.org 1362731285 18363 80.91.229.3 (8 Mar 2013 08:28:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 8 Mar 2013 08:28:05 +0000 (UTC) Cc: Lele Gaifax , emacs-devel@gnu.org, emacs-orgmode@gnu.org, Bastien To: Xue Fuqiao Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 08 09:28:27 2013 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 1UDsfB-0003KN-Ve for ged-emacs-devel@m.gmane.org; Fri, 08 Mar 2013 09:28:26 +0100 Original-Received: from localhost ([::1]:45955 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDseq-0008B0-5r for ged-emacs-devel@m.gmane.org; Fri, 08 Mar 2013 03:28:04 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:36246) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDsem-0008Ap-JB for emacs-devel@gnu.org; Fri, 08 Mar 2013 03:28:02 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UDsel-00067w-By for emacs-devel@gnu.org; Fri, 08 Mar 2013 03:28:00 -0500 Original-Received: from mgmt2.sk.tsukuba.ac.jp ([130.158.97.224]:38669) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UDsel-00067j-1c; Fri, 08 Mar 2013 03:27:59 -0500 Original-Received: from uwakimon.sk.tsukuba.ac.jp (uwakimon.sk.tsukuba.ac.jp [130.158.99.156]) by mgmt2.sk.tsukuba.ac.jp (Postfix) with ESMTP id 9DC3F970860; Fri, 8 Mar 2013 17:27:56 +0900 (JST) Original-Received: by uwakimon.sk.tsukuba.ac.jp (Postfix, from userid 1000) id 633BB11F432; Fri, 8 Mar 2013 17:27:56 +0900 (JST) In-Reply-To: <513997AD.5050901@gmail.com> X-Mailer: VM undefined under 21.5 (beta32) "habanero" b0d40183ac79 XEmacs Lucid (x86_64-unknown-linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 130.158.97.224 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:157584 gmane.emacs.orgmode:67910 Archived-At: Xue Fuqiao writes: > On 03/08/2013 02:40 PM, Bastien wrote: > > I missed the distinction between "pretest" and "release candidate". > > What's the difference between "pretest" and "release candidate"? A release candidate may be considered to be a kind of pretest. The difference (as Glenn already implied) is that in a release candidate the release engineer proposes to make exactly one change before release: remove "rc" from the version string and then roll the tarballs and announce. Only if the release is unusable (new crash, data corruption, or security hole since last pretest) will it be patched before release. The way to think about this is that a release candidate is only there to save face for the release engineer. Ordinary bugs aren't his problem any more. ;-)