emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniele Nicolodi <daniele@grinta.net>
To: emacs-orgmode@gnu.org
Subject: Re: Release Org 9.4.2
Date: Tue, 15 Dec 2020 22:12:13 +0100	[thread overview]
Message-ID: <5b65f871-655a-1048-7a53-c0c794fe2abb@grinta.net> (raw)
In-Reply-To: <873607yxvh.fsf@codeisgreat.org>

On 15/12/2020 14:58, Pankaj Jangid wrote:
> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> 
>> On Monday, 14 Dec 2020 at 20:49, Pankaj Jangid wrote:
>>> 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. 
>>
>> Or you could track org development from git just as you are tracking
>> Emacs.  That's what I do: any time I build the most recent Emacs (maybe
>> every 2-3 weeks), I also build org.
> 
> May be that I am not explaining it well. Let me put it in a question
> format. It is possible that this has been discussed and I appologise for
> my ignorance.
> 
> My question is/are: (1) Why Org is developed outside Emacs, given that
> it is a core/built-in package. (2) Are there other packages that follow
> the same process?

AFAIK also cc-mode is developed in a dedicate repository.

From an Emacs development point of view there is the desire to move more
packages that are now included in the core to ELPA and assemble Emacs
releases from these. This will allow packages to have independent
releases and users to update them more frequently than the pace of Emacs
releases. In this process, moving more packages to separate git
repositories would be natural. Thus, the idea would be remove the need
for syncing the org and cc-mode codebases to the Emacs repository rather
than moving the development of these packages to the Emacs git.

Cheers,
Dan


  parent reply	other threads:[~2020-12-15 21:12 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14  7:04 Bastien
2020-12-14 14:10 ` Pankaj Jangid
2020-12-14 14:18   ` Bastien
2020-12-14 15:19     ` Pankaj Jangid
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 [this message]
2020-12-16  5:19             ` Pankaj Jangid
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=5b65f871-655a-1048-7a53-c0c794fe2abb@grinta.net \
    --to=daniele@grinta.net \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Release Org 9.4.2' \
    /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

Code repositories for project(s) associated with this 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).