From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Reuben Thomas <rrt@sc3d.org>
Cc: Josiah Schwab <jschwab@gmail.com>, Bastien Guerry <bzg@gnu.org>,
"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 15:56:08 +0100 [thread overview]
Message-ID: <87ins8ftyv.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAOnWdohmOnjfB+kWnz0PJFVSjhQHg=uipU592Jp3fitLrR2kDA@mail.gmail.com> (Reuben Thomas's message of "Mon, 31 Oct 2016 11:44:03 +0000")
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.
However, I think we should make more frequent bugfix releases. We may
even automate such releases, e.g., one week after the last unreleased
bugfix in the branch. I don't do releases however, so this may just be
a weird idea.
Bastien, is it even possible?
> 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
> I can't imagine there are many users who would prefer to compile from
> source rather than just use package-install!
I don't think we force users to use development version (even though it
is appreciated, particularly close to a major release). OTOH, being able
to browse source code is very important so the "git clone" command and
the "cgit" link also belong to the first page.
> 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.
We need to tell the difference between a release and a cut from the
maint branch.
Also, I'd rather have monotonic version tags, so 8.3.6.whatever is not
really an option. Maybe 8.3.YYYMMDD... and we drop manual bugfix
releases altogether.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-10-31 14:56 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 [this message]
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=87ins8ftyv.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=jschwab@gmail.com \
--cc=rrt@sc3d.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).