emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tftorrey@tftorrey.com (T.F. Torrey)
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bleeding edge in elpa
Date: Sun, 08 Mar 2015 23:48:31 -0700	[thread overview]
Message-ID: <874mpuvf7k.fsf@jack.tftorrey.com> (raw)
In-Reply-To: <871tkzb9i1.fsf@gmx.us> (message from Rasmus on Sun, 08 Mar 2015 19:59:50 +0100)

Hello,

Rasmus <rasmus@gmx.us> writes:

> As I think somebody said, the correct "fix" to this problem is more
> frequent released.  I'm sure Bastien would appreciate help with this.
> Do you want to volunteer?

If the goal is to have the latest and greatest version of Org available via
ELPA (for all the reasons some people use ELPA instead of git), there
are two obvious options:

1. Org could have a stable release every month or so.

2. The Org server could be configured to automatically package the
master version of Org every day, as the maint version is now.

Option 1 is widely regarded as the best choice.  However, it requires a
lot of actual, repeated human effort.  As Debian repeatedly
demonstrates, this is very hard to do, even once.  If option 1 could be
done, it would already be done.

Option 2 would be a one-time (mostly) human effort, and the daily work
would be automated.

So, if the goal is to have the latest and greates version of Org
available via ELPA (and it should be), option 2 is the only one that is
possible in the real world, so that's the one we should set up.

All the best,
Terry
--
T.F. Torrey

  reply	other threads:[~2015-03-09  8:14 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
2015-03-08 18:59         ` Rasmus
2015-03-09  6:48           ` T.F. Torrey [this message]
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=874mpuvf7k.fsf@jack.tftorrey.com \
    --to=tftorrey@tftorrey.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).