From: Reuben Thomas <rrt@sc3d.org>
To: Reuben Thomas <rrt@sc3d.org>, Josiah Schwab <jschwab@gmail.com>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>,
Bastien Guerry <bzg@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 19:45:53 +0000 [thread overview]
Message-ID: <CAOnWdohoBRRc70JxWwEfs1GGA9LwcMWEatxRcKM-bS==Y6GT9A@mail.gmail.com> (raw)
In-Reply-To: <87ins8ftyv.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
On 31 October 2016 at 14:56, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Reuben Thomas <rrt@sc3d.org> writes:
>
> > That's great! However, is a cut of the release branch as good as an
> actual
> > release?
>
> It is better, since it contains more bugfixes than last release without
> adding new features.
>
That's good to know.
> Thought experiment: if it is good enough, surely the web site should
> > point users to this installation method for the stable version?
>
> Isn't it the case already? From the first page I see
>
> M-x list-packages RET (see Org ELPA)
>
> Daily snapshots: tar.gz or zip
>
The web page is quite clear. Under "Download and install" you can get
"Stable version" (only from source), or "Development version" (cgit or M_x
list-packages RET), or "Daily snapshots".
In other words, it looks as though the Org ELPA version is a development
version. The linked page does nothing to counter this impression.
I suggest that the "M-x list-packages RET" part be moved up the page to
"Stable version"; it should say something like:
"Stable version: M-x list-packages RET (see Org ELPA; includes fixes since
last release), or tar.gz or zip (release notes).
Ideally there would be up-to-date release notes for the ELPA version, so
that users can see which bugs are fixed. This should be easy if there is a
partially-completed release notes file in preparation for the next release.
In other words, the ELPA method should be highlighted as the preferred
method of installation, and it should be made obvious that it's stable
(this is why I think it's important to change the version of the ELPA
package to contain the version number; by the way, considering it as a
semver version number, it already is monotonic).
Being able to install org-mode stable from ELPA is something I've wanted
for years without realising it is already available! I bet I'm not the only
one…
--
http://rrt.sc3d.org
[-- Attachment #2: Type: text/html, Size: 3712 bytes --]
next prev parent reply other threads:[~2016-10-31 19:45 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
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 [this message]
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='CAOnWdohoBRRc70JxWwEfs1GGA9LwcMWEatxRcKM-bS==Y6GT9A@mail.gmail.com' \
--to=rrt@sc3d.org \
--cc=bzg@gnu.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).