From: "Eric Schulte" <schulte.eric@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Dan Davison <davison@stats.ox.ac.uk>,
John Wiegley <jwiegley@gmail.com>,
Org Mode List <emacs-orgmode@gnu.org>,
Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: FEATURE FREEZE, for a short time
Date: Fri, 02 Jul 2010 12:00:01 -0700 [thread overview]
Message-ID: <87iq4xr9ou.fsf@gmail.com> (raw)
In-Reply-To: <AF88FFEC-CFD3-4A3F-81FD-120CD541D3B9@gmail.com> (Carsten Dominik's message of "Fri, 2 Jul 2010 16:18:01 +0200")
Carsten Dominik <carsten.dominik@gmail.com> writes:
[...]
>
> P.S. Eric and Dan, please decide yourself how to get to
> a good and stable state in this time frame, babel integration
> is by far the biggest thing in this release.
Hi Carsten,
I'm looking forward to a feature-quiet period of stabilization. There
is one more large Babel change before 7.0, namely the integration of the
safety measures currently living in the "safety-babel" branch [1]. I
think that it would be best if these are merged into Org-mode at the
start of this feature freeze so that they can be tested during this
period. Please let me know if this sounds good to you, and if so I will
send out one last email alerting Babel users to the requirement for a
configuration change [2], and then merge in these two new commits.
Thanks -- Eric
Footnotes:
[1] http://repo.or.cz/w/org-mode.git/shortlog/refs/heads/safety-babel
[2] I do apologize for the number of configuration breaking changes
that have been made to Babel recently. I know the pain of starting
up Emacs, running into an unexpected failure, and then having to
make time to trouble-shoot before you can actually get any work
done.
Once this merge is over I see many months of smooth Babel sailing
on the horizon.
prev parent reply other threads:[~2010-07-02 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 14:18 FEATURE FREEZE, for a short time Carsten Dominik
2010-07-02 19:00 ` Eric Schulte [this message]
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=87iq4xr9ou.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=bastien.guerry@wikimedia.fr \
--cc=carsten.dominik@gmail.com \
--cc=davison@stats.ox.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=jwiegley@gmail.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).