From: Aaron Ecay <aaronecay@gmail.com>
To: "T.F. Torrey" <tftorrey@tftorrey.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bleeding edge in elpa
Date: Tue, 10 Mar 2015 23:51:48 -0300 [thread overview]
Message-ID: <87y4n4l1bj.fsf@gmail.com> (raw)
In-Reply-To: <878uf4ilpq.fsf@jack.tftorrey.com>
Hi Terry,
2015ko martxoak 10an, "T.F. Torrey"-ek idatzi zuen:
> Of the things in your list, I think only the NEWS and Changelog are
> absent from the master branch in git. Lots of us happily use Org master
> from git without them every day. Do they really need to be done at
> all?
Many people are very happy not using org at all. Perhaps we should just
all quit and find other hobbies. OTOH, release milestones are important
to the health of a software project and so yes, really need to be done.
>
> If Emacs 25 is taking Org out of core, does the code still have to be
> merged into the trunk?
This is not on the table. Rather, the (tentative) proposal from the
emacs side is for some packages to be developed in the GNU ELPA
repository, and be extracted from there and bundled with emacs release
tarballs (in addition to being released in ELPA).
Org is sometimes cited as an example of a package that would benefit from
this strategy, but there has been no discussion of this from the org
side, and AFAIK no decision has been made whether we’d take advantage of
this facility if/when it’s available.
>
> If the manpower does not exist to support both a maint and a master
> branch, maybe they should be merged. Could that be done?
>
> Still just trying to make it easier to spread the gospel of Org,
Exposing new users to the vagaries of the master branch may rather lead
to atheism.
--
Aaron Ecay
next prev parent reply other threads:[~2015-03-11 2:52 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
2015-03-10 1:57 ` Aaron Ecay
2015-03-10 21:30 ` T.F. Torrey
2015-03-11 2:51 ` Aaron Ecay [this message]
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=87y4n4l1bj.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tftorrey@tftorrey.com \
/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).