From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nikolai Weibull Subject: Re: Bleeding edge in elpa Date: Sun, 8 Mar 2015 19:34:29 +0100 Message-ID: References: <87ioebmvex.fsf@gmail.com> <87d24jqsj9.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52956) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YUg23-0003Jo-Hh for emacs-orgmode@gnu.org; Sun, 08 Mar 2015 14:34:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YUg22-0002aM-Ix for emacs-orgmode@gnu.org; Sun, 08 Mar 2015 14:34:31 -0400 Received: from mail-we0-x22a.google.com ([2a00:1450:400c:c03::22a]:46871) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YUg22-0002aG-Cs for emacs-orgmode@gnu.org; Sun, 08 Mar 2015 14:34:30 -0400 Received: by wevm14 with SMTP id m14so69731509wev.13 for ; Sun, 08 Mar 2015 11:34:29 -0700 (PDT) In-Reply-To: <87d24jqsj9.fsf@Rainer.invalid> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Achim Gratz Cc: emacs-orgmode@gnu.org On Sun, Mar 8, 2015 at 6:59 PM, Achim Gratz 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 >> =E2=80=9Cversion=E2=80=9D would lessen the effect of this. It would als= o 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 =E2=80=9Corg=E2=80=9D package as it is today (bas= ed off of maint) and an =E2=80=9Corg-edge=E2=80=9D package that=E2=80=99d be based of= f of master.