From: Reuben Thomas <rrt@sc3d.org>
To: Josiah Schwab <jschwab@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)]
Date: Mon, 31 Oct 2016 11:44:03 +0000 [thread overview]
Message-ID: <CAOnWdohmOnjfB+kWnz0PJFVSjhQHg=uipU592Jp3fitLrR2kDA@mail.gmail.com> (raw)
In-Reply-To: <87oa21tmp0.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
On 30 October 2016 at 23:57, Josiah Schwab <jschwab@gmail.com> wrote:
> Hi Reuben,
>
> > It would be great if it were possible to install stable org-mode
> > versions from GNU ELPA or MELPA Stable. At present, one has to choose
> > between installing bleeding-edge versions simply, or stable versions
> > built by hand.
> >
> > (I am a bit surprised I can’t find anything about this in the mailing
> > list archives, so do forgive me if I’ve overlooked previous discussion.)
>
> The version on GNU ELPA (http://elpa.gnu.org/packages/org.html), which
> is labeled org-20161024, is org-git-version 8.3.6-7-g4d7d52-elpa.
>
> I believe that indicates that it is the latest version from the stable
> maint branch, not a version from the unstable master branch (which is at
> 8.3.6-1264-g21932c right now).
>
That's great! However, is a cut of the release branch as good as an actual
release?
Thought experiment: if it is good enough, surely the web site should
point users to this installation method for the stable version? I can't
imagine there are many users who would prefer to compile from source rather
than just use package-install!
Also, the version should be the git tag (so that the version number is
clearly visible), rather than the current "YYYYMMDD" format, which looks
like a development snapshot.
If the org-mode maintainers do *not* consider these release branch
snapshots to be as good as actual releases, then I would repeat my request
for stable releases to be available on GNU ELPA or MELPA Stable.
--
http://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 2730 bytes --]
next prev parent reply other threads:[~2016-10-31 11:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 22:30 Bug: Please supply stable releases on ELPA or MELPA Stable [8.3.4 (8.3.4-dist @ /usr/local/share/emacs/25.1.50/site-lisp/org-mode/)] Reuben Thomas
2016-10-30 23:57 ` Josiah Schwab
2016-10-31 11:44 ` Reuben Thomas [this message]
2016-10-31 14:56 ` Nicolas Goaziou
2016-10-31 18:52 ` Achim Gratz
2016-10-31 19:06 ` Nicolas Goaziou
2016-10-31 19:45 ` Reuben Thomas
2016-11-01 10:32 ` Bastien Guerry
2016-11-01 10:59 ` Reuben Thomas
2016-11-01 17:01 ` Bastien Guerry
2016-11-01 23:01 ` Reuben Thomas
2016-11-02 8:18 ` Bastien Guerry
2016-11-01 10:27 ` Bastien Guerry
2016-11-01 11:08 ` Nicolas Goaziou
2016-11-01 15:28 ` Bastien Guerry
2016-11-01 17:33 ` Achim Gratz
2016-11-01 23:43 ` Nicolas Goaziou
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='CAOnWdohmOnjfB+kWnz0PJFVSjhQHg=uipU592Jp3fitLrR2kDA@mail.gmail.com' \
--to=rrt@sc3d.org \
--cc=emacs-orgmode@gnu.org \
--cc=jschwab@gmail.com \
/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).