emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Allen Li <darkfeline@felesatra.moe>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Starting from 9.5, Org contrib will be distributed as a separate NonGNU ELPA package
Date: Tue, 30 Mar 2021 17:30:26 -0700	[thread overview]
Message-ID: <80im58np0d.fsf@felesatra.moe> (raw)
In-Reply-To: <87a6qnixnr.fsf@gnu.org> (Bastien's message of "Sun, 28 Mar 2021 08:45:44 +0200")

Bastien <bzg@gnu.org> writes:

> Hi all,
> starting from Org 9.5, org-contrib will be distributed as a NonGNU
> ELPA package.  You will find it here: https://elpa.nongnu.org/nongnu/
> See for https://orgmode.org/list/87wnzfy60h.fsf@bzg.fr/ for context.
> Thanks,

Will there be an overlapping period (and if not, can we add such a
period)?  For example, have one release where org-contrib is still
shipped, and the NonGNU repos are available.  That gives users such as
myself a period to switch over without things breaking immediately.

If I understand correctly, the current plan is that users using
org-contrib will have their configs break immediately when they upgrade
to 9.5, forcing them to do both the 9.5 upgrade and switchover to NonGNU
simultaneously.  It's easier if we can first safely upgrade to 9.5, then
switch to NonGNU repos, and in the next release org-contrib can be removed.

  parent reply	other threads:[~2021-03-31  0:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-28  6:45 Starting from 9.5, Org contrib will be distributed as a separate NonGNU ELPA package Bastien
2021-03-28 13:31 ` Colin Baxter
2021-03-28 15:20   ` Bastien
2021-03-28 15:34     ` Colin Baxter
2021-03-31  0:30 ` Allen Li [this message]
2021-03-31  0:42   ` Tim Cross
2021-04-11 12:46   ` Bastien
2021-04-11 21:46     ` Samuel Wales
2021-04-12  5:20       ` Bastien
2021-04-12  5:32         ` Samuel Wales
2021-04-12  5:50           ` Bastien

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:

  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=80im58np0d.fsf@felesatra.moe \
    --to=darkfeline@felesatra.moe \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).