From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: Stable releases Date: Wed, 12 Aug 2015 19:37:32 +0200 Message-ID: <87bnec9zmr.fsf@Rainer.invalid> References: <55CA2E6B.4060102@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:42102) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZPZyA-0002CS-Ni for emacs-orgmode@gnu.org; Wed, 12 Aug 2015 13:37:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZPZy7-0002ru-70 for emacs-orgmode@gnu.org; Wed, 12 Aug 2015 13:37:42 -0400 Received: from plane.gmane.org ([80.91.229.3]:35314) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZPZy7-0002rW-0p for emacs-orgmode@gnu.org; Wed, 12 Aug 2015 13:37:39 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZPZy5-0007eU-JI for emacs-orgmode@gnu.org; Wed, 12 Aug 2015 19:37:37 +0200 Received: from p54b46a4b.dip0.t-ipconnect.de ([84.180.106.75]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Aug 2015 19:37:37 +0200 Received: from Stromeko by p54b46a4b.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Aug 2015 19:37:37 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Scott Randby writes: > While I've used Org's development version in the past, I stopped doing > that due to my failure to learn how to use git (no time) and other > issues. Now, I only use the stable releases. But the latest 8.3 > release doesn't seem so stable to me, so I'd like some clarification > about what the Org maintainers mean by a stable release. Perhaps this > is too vague, so let me explain a bit. There are no stable releases, but major and minor ones (see README_maintainer). Major releases are developed in the master branch and include backwards-incompatible changes as well as new and removed features. Minor releases are made from the maint branch and are kept backwards compatible to the last major release (only bug fixes, no new features, no feature removal). > Normally, I wait many months before upgrading Org to a new stable > release, but when 8.3 was released, I upgraded right away (from > 8.2.10) since I have a new machine on which I installed Emacs 24.5. I > read through the release notes for anything that might give me > problems and didn't see anything. Since the NEWS file isn't automatically generated, there are some holes to be expected after two years of development. That's not an excuse, mind you, and everyone should strive to be more diligent in keeping the code changes synced up with the documentation. > I guess what I want to know, and maybe there is no answer, is how long > should I wait before upgrading to a stable release? Org is by far the > most important piece of software I use (I hate it when I can't use > Org), and bugs (which I know can't be avoided) make it hard, even > impossible, for me to get my real work done. If there is a way for me > to minimize encountering bugs, I will appreciate a description of that > way. As always when it comes to updates, there is the camp that says you should keep with the flow and make many small changes in doing so and the other one that says to wait unltil the last moment and then do the big-bang change of everything. In your case it seems you need to plan for some conversion time whenever you skip to a new major release. I don't see why you would skip minor releases though. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs