[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Bleeding edge in elpa

From: Achim Gratz
Subject: Re: [O] Bleeding edge in elpa
Date: Sun, 08 Mar 2015 18:59:38 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux)

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.

> 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).

> 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.  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.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf rackAttack V1.04R1:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]