From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Release Org 9.4.2
Date: Mon, 14 Dec 2020 20:49:45 +0530 [thread overview]
Message-ID: <87h7ooxvn2.fsf@codeisgreat.org> (raw)
In-Reply-To: <873608o4h8.fsf@bzg.fr> (Bastien's message of "Mon, 14 Dec 2020 15:18:59 +0100")
Bastien <bzg@gnu.org> writes:
>>> I've released Org 9.4.2, a bugfix release.
>>>
>>> This version was merged with the emacs-27 branch:
>>
>> This is the only code that goes into stable branch first and then into
>> ‘master’. Probably we need tweak the process a bit.
>
> Sorry, I don't understand your concern here. What should be done
> differently?
Sorry for not being elaborate. Actually, I had posted serveral days ago
in another thread as well that probably we should consider emacs-master
for the active development of Org.
I like testing Emacs on the trunk and I ‘git pull’ and ‘make bootstrap’
daily and use it without any external packages. This is just to make
sure that any external package is not the cause for what appears to be
an Emacs bug.
I can certainly add latest Org by adding it to the package-archives. But
right now there is no point. I like to be on the bleeding edge. But I
also like to contribute at least by testing the next major release of
Emacs. And I am not sure whether the latest snapshot of Org from
https://orgmode.org/elpa will be part of next major release of Emacs,
whenever that happens.
Org will also benefit from the wider testing if the incremental changes
are part of everyone’s daily build of emacs-master.
In addition to master, we can release versions via GNU ELPA. That way
users won’t have to tweak their package-archives. Core packages should
not require making changes to package-archives.
I know you are overloaded with tasks at present. So I am not asking that
we do these things rightaway. But somewhere down the line Emacs and Org
development must converge.
Hope to see Org 9.4.2 in master soon. :-)
next prev parent reply other threads:[~2020-12-14 18:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 7:04 Release Org 9.4.2 Bastien
2020-12-14 14:10 ` Pankaj Jangid
2020-12-14 14:18 ` Bastien
2020-12-14 15:19 ` Pankaj Jangid [this message]
2020-12-15 11:38 ` Eric S Fraga
2020-12-15 13:58 ` Pankaj Jangid
2020-12-15 14:24 ` Bastien
2020-12-16 3:59 ` Pankaj Jangid
2020-12-16 6:19 ` Bastien
2020-12-16 7:00 ` Pankaj Jangid
2020-12-16 7:14 ` TEC
2020-12-16 13:04 ` Gustav Wikström
2020-12-16 13:49 ` Eric S Fraga
2020-12-16 14:11 ` Gustav Wikström
2020-12-16 14:50 ` Eric S Fraga
2020-12-16 15:05 ` Gustav Wikström
2020-12-29 9:42 ` TEC
2020-12-29 12:14 ` Gustav Wikström
2020-12-16 15:13 ` Loris Bennett
2020-12-16 19:01 ` Tim Cross
2020-12-17 13:27 ` Eric S Fraga
2020-12-17 15:32 ` Greg Minshall
2020-12-17 23:19 ` Samuel Wales
2020-12-16 14:56 ` Pankaj Jangid
2020-12-16 18:41 ` Tim Cross
2020-12-22 14:27 ` Lennart C. Karssen
2020-12-22 15:07 ` TEC
2020-12-22 16:18 ` Bastien
2020-12-22 19:46 ` Jean Louis
2020-12-15 21:12 ` Daniele Nicolodi
2020-12-16 5:19 ` Pankaj Jangid
-- strict thread matches above, loose matches on Subject: below --
2020-12-18 21:49 Asa Zeren
2020-12-21 12:25 ` Eric S Fraga
2021-01-02 22:45 ` TRS-80
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=87h7ooxvn2.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@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 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).