From: Rasmus <rasmus@gmx.us>
To: eliz@gnu.org
Cc: bzg@gnu.org, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-26 613c9a5: Update Org to v9.1.9
Date: Sat, 07 Apr 2018 21:05:10 +0200 [thread overview]
Message-ID: <87in92g7mh.fsf@gmx.us> (raw)
In-Reply-To: <831sfx7pe4.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 02 Apr 2018 15:40:19 +0300")
Hi Eli,
Thanks for the explanation.
Eli Zaretskii <eliz@gnu.org> writes:
>> >> Update Org to v9.1.9
>> >>
>> >> Please note this is a bugfix release. See etc/ORG-NEWS for details.
>> >
>> > Thanks, but this merge should have been discussed first. Most of its
>> > changes are no-brainers, but some are non-trivial, and we should have
>> > talked about them before the merge, to make sure we understand all the
>> > tradeoffs, and indeed the changes are safe for Emacs 26.1.
>>
>> These should all be bugfixes and should not alter features. In general,
>> minor release changes relate to bug reports on the Org mailing list or
>> debbugs.
>
> I understand, but experience taught me that different people tend to
> see bugfixes from different perspectives and assess their risks
> differently. It's quite possible that, have you described the
> non-trivial changes, we'd all agree that they are safe enough. But it
> could be that some of them would have been considered too risky.
I am happy to put together a change log if that would be helpful. We have
a change log entry for each change.
In the future, if we are close to a release I’ll obviously ping the list
before merging a new version, even if deemed minor from the Org devs point
of view.
Thanks,
Rasmus
--
Lasciate ogni speranza o voi che entrate: siete nella mani di'machellaio
next prev parent reply other threads:[~2018-04-07 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.35838.1522186736.27993.emacs-diffs@gnu.org>
2018-03-29 12:30 ` [Emacs-diffs] emacs-26 613c9a5: Update Org to v9.1.9 Eli Zaretskii
2018-04-02 12:30 ` Rasmus
2018-04-02 12:40 ` Eli Zaretskii
2018-04-07 19:05 ` Rasmus [this message]
2018-04-07 19:12 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87in92g7mh.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=bzg@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.