From: Nikolai Weibull <now@disu.se>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bleeding edge in elpa
Date: Sun, 8 Mar 2015 19:34:29 +0100 [thread overview]
Message-ID: <CADdV=MvJTgyg5yTP9wMVMtFjKEg-VDgOyNHOqiZTY7ncmML8og@mail.gmail.com> (raw)
In-Reply-To: <87d24jqsj9.fsf@Rainer.invalid>
On Sun, Mar 8, 2015 at 6:59 PM, Achim Gratz <Stromeko@nexgo.de> wrote:
> Nikolai Weibull writes:
>> Is trying to manage it via git+make oneself less likely to cause
>> incidents?
> There's a bunch of people who seem to manage it just fine.
Did I say otherwise?
Does this preclude making an alternative available, one that at least
some would consider simpler to access?
>> 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.
> Yes, if the absolutely latest master doesn't work, people can just check
> out whatever version was working for them last and continue without
> waiting for the next snapshot from ELPA /which may or may not work).
See below.
>> 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.
> It doesn't get any easier than it already is.
(How can this statement possibly be true?)
> Having both a stable and
> an unstable version of Org avilable via ELPA is a non-starter for the
> simple reason that the package manager can't deal with the versioning
> problems this would introduce.
This could, I assume, and was sort of implied in my original e-mail,
be solved by providing an “org” package as it is today (based off of
maint) and an “org-edge” package that’d be based off of master.
next prev parent reply other threads:[~2015-03-08 18:34 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
2015-03-08 17:59 ` Achim Gratz
2015-03-08 18:34 ` Nikolai Weibull [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADdV=MvJTgyg5yTP9wMVMtFjKEg-VDgOyNHOqiZTY7ncmML8og@mail.gmail.com' \
--to=now@disu.se \
--cc=Stromeko@nexgo.de \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.