From: Bastien Guerry <bzg@gnu.org>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-org list <emacs-orgmode@gnu.org>,
Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: Release Org 9.1 soon ?
Date: Sun, 27 Aug 2017 14:32:55 +0200 [thread overview]
Message-ID: <87d17h42dk.fsf@bzg.fr> (raw)
In-Reply-To: <87wp5puz6v.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 27 Aug 2017 11:39:36 +0200")
Hi Kaushal and Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> There's no hurry anyways. I don't consider this to be a blocker for Org
> 9.1. Of course, it is better if it can be integrated before.
If org-set-tags is to be rewritten, we need to carefully test the
rewrite before integrating it. So 9.2 is a decent goal for it,
assuming 9.2 will be closer to 9.1 than 9.1 to 9.0.
> Please do, but first, why do you think it is better to have it in core
> instead of, e.g., GNU Elpa? Doesn't "ox-publish" provide some static
> site generation features already?
>
> Also, "ox-hugo" requires "ox-blackfriday", which is another Markdown
> back-end. I'm not questioning the usefulness of this package, but
> I think we need very good reasons to provide overlapping features out of
> the box.
Indeed. Again, the biggest issue here is that of discoverability,
and moving code into core is the simplest way, but not necessarily
the better. We can expect new exporters to live in GNU ELPA (or
elsewhere) first, then to be included in core is there is a strong
support and a strong need for it.
--
Bastien
next prev parent reply other threads:[~2017-08-27 12:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 8:18 Release Org 9.1 soon ? Nicolas Goaziou
2017-08-26 12:30 ` Kaushal Modi
2017-08-27 1:25 ` Nicolas Goaziou
2017-08-27 1:53 ` Kaushal Modi
2017-08-27 9:39 ` Nicolas Goaziou
2017-08-27 12:32 ` Bastien Guerry [this message]
2017-08-27 12:27 ` Bastien Guerry
2017-08-27 12:24 ` Bastien Guerry
2017-08-27 13:11 ` Nicolas Goaziou
2017-08-27 14:23 ` Bastien Guerry
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=87d17h42dk.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=mail@nicolasgoaziou.fr \
/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).