From: Nikolai Weibull <now@disu.se>
To: Nikolai Weibull <now@disu.se>, emacs-orgmode@gnu.org
Subject: Re: Bleeding edge in elpa
Date: Sun, 8 Mar 2015 18:24:23 +0100 [thread overview]
Message-ID: <CADdV=MsxMDorr4LG3gSyyY0D9UyvW_n8LLj4NyXgKFX9JOGiXw@mail.gmail.com> (raw)
In-Reply-To: <87ioebmvex.fsf@gmail.com>
On Sun, Mar 8, 2015 at 3:17 PM, Aaron Ecay <aaronecay@gmail.com> wrote:
> IMO this is a bad idea. The bleeding edge version is expected to be
> somewhat unstable, and exposing it via ELPA will lead to foot-shooting
> incidents.
Is trying to manage it via git+make oneself less likely to cause incidents?
From the FAQ:
The master branch of the git repository always contains the bleeding
edge development code. This is important for Org's fast development,
because code on master gets checked out by many people daily and we
quickly receive bug reports if something is wrong. On rare occasions,
this code may not function perfectly for a limited time while we are
trying to fix things. It is therefore recommended to keep a known-good
version of org-mode installed outside the source tree and always run
the full test suite before using a new version from master.
> On the other hand, it would be nice to have more regular releases from
> master to maint. AFAIK the last one was a year and a half ago (Org
> 8.2). However, this has traditionally required a lot of effort from
> Bastien and others, so it’s not a simple case of “wishing will make it
> so”.
The more time that passes between releases, the harder it is to
release a new version.
And as this is the case here, having easy access to the latest
“version” would lessen the effect of this. It would also allow more
people to find bugs.
next prev parent reply other threads:[~2015-03-08 17:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 14:36 Bleeding edge in elpa Nikolai Weibull
2015-03-07 14:47 ` Xavier Maillard
2015-03-07 16:09 ` Nikolai Weibull
2015-03-08 5:48 ` Xavier Maillard
2015-03-09 9:08 ` Sebastien Vauban
2015-03-09 16:24 ` T.F. Torrey
2015-03-07 15:40 ` Grant Rettke
2015-03-07 21:44 ` T.F. Torrey
2015-03-08 1:32 ` Nicolas Girard
2015-03-08 14:17 ` Aaron Ecay
2015-03-08 17:24 ` Nikolai Weibull [this message]
2015-03-08 17:59 ` Achim Gratz
2015-03-08 18:34 ` Nikolai Weibull
2015-03-08 18:59 ` Rasmus
2015-03-09 6:48 ` T.F. Torrey
2015-03-10 1:57 ` Aaron Ecay
2015-03-10 21:30 ` T.F. Torrey
2015-03-11 2:51 ` Aaron Ecay
2015-03-11 19:18 ` T.F. Torrey
2015-03-11 19:59 ` Nick Dokos
2015-03-09 7:53 ` T.F. Torrey
2015-03-09 18:24 ` Achim Gratz
2015-03-09 19:21 ` T.F. Torrey
2015-03-10 11:01 ` Alexis
2015-03-10 15:21 ` Grant Rettke
2015-03-08 18:09 ` T.F. Torrey
2015-03-08 19:57 ` Rasmus
2015-03-08 20:20 ` Achim Gratz
2015-03-08 20:27 ` Rasmus
2015-03-08 20:36 ` Achim Gratz
2015-03-09 8:13 ` T.F. Torrey
2015-03-09 7:31 ` T.F. Torrey
2015-03-10 2:01 ` Richard Y. Kim
2015-03-10 6:29 ` Achim Gratz
2015-03-10 21:21 ` T.F. Torrey
2015-03-10 20:20 ` T.F. Torrey
2015-08-05 0:00 ` Bastien Guerry
2015-03-10 10:51 ` Steinar Bang
2015-03-10 17:11 ` Achim Gratz
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='CADdV=MsxMDorr4LG3gSyyY0D9UyvW_n8LLj4NyXgKFX9JOGiXw@mail.gmail.com' \
--to=now@disu.se \
--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).