From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Org-mode version number Date: Mon, 17 Nov 2008 08:06:44 +0100 Message-ID: <1EA9C090-527C-4EDC-B7FF-36123A6B8B58@uva.nl> Mime-Version: 1.0 (Apple Message framework v929.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L1yoq-0002PT-RZ for emacs-orgmode@gnu.org; Mon, 17 Nov 2008 02:46:48 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L1yoo-0002NY-JR for emacs-orgmode@gnu.org; Mon, 17 Nov 2008 02:46:47 -0500 Received: from [199.232.76.173] (port=57236 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L1yoo-0002NV-F7 for emacs-orgmode@gnu.org; Mon, 17 Nov 2008 02:46:46 -0500 Received: from ug-out-1314.google.com ([66.249.92.168]:41794) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1L1yoo-0006Hl-14 for emacs-orgmode@gnu.org; Mon, 17 Nov 2008 02:46:46 -0500 Received: by ug-out-1314.google.com with SMTP id 36so407351uga.17 for ; Sun, 16 Nov 2008 23:46:45 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: orgmode Org-Mode Hi, I want to clarify the version numbers I am using for org-mode. Some of this system was used already in the past, but in the future I will implement it more rigorously: Major releases have version numbers like 6.12. Small cleanup-releases quickly after a major release will be 6.12a, 6.12b, ... During the development period between two releases, the version number will look like this: 6.12trans. That means this is after 6.12x. In the run-up to a release, version numbers will be like 6.13pre01. During this time I am trying to avoid new features, only polishing and documenting what is there. Note that most of these version numbers uniquely identify a version. However, the "trans" version numbers applies to many different steps, and during this time, the only way to uniquely identify the version you are using is through the sha1 of the git commit. - Carsten