emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: orgmode Org-Mode <emacs-orgmode@gnu.org>
Subject: Org-mode version number
Date: Mon, 17 Nov 2008 08:06:44 +0100	[thread overview]
Message-ID: <1EA9C090-527C-4EDC-B7FF-36123A6B8B58@uva.nl> (raw)

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

                 reply	other threads:[~2008-11-17  7:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1EA9C090-527C-4EDC-B7FF-36123A6B8B58@uva.nl \
    --to=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).