From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Stephen J. Turnbull" 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: In-Reply-To: <513997AD.5050901@gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org To: Xue Fuqiao Cc: Lele Gaifax , emacs-devel@gnu.org, emacs-orgmode@gnu.org, Bastien List-Id: emacs-orgmode.gnu.org 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. ;-)