emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TEC <tecosaur@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Are we still in a feature freeze?
Date: Thu, 03 Sep 2020 18:37:19 +0800	[thread overview]
Message-ID: <87o8mnxi1t.fsf@gmail.com> (raw)
In-Reply-To: <87k0xbywxq.fsf@gnu.org>

Hi Bastien!

Great to see you back on the lists again :)

Bastien <bzg@gnu.org> writes:

> Good guess :)   I'm rolling up my sleeves to get to 9.4 ASAP so that
> we can commit features in the master branch again soonish.
> Still, you can share patches on the list, that's useful to discuss
> and improve them.

I won't hold back till 9.4 is released then, thanks for confirming the status.

> We do not use code.orgmode.org for collaborative development, we
> use this list instead.  You can still create a clone of Org where
> you see fit.

Ah, I see. I was going off a line in https://orgmode.org/worg/org-contribute.html
"If you are undertaking big changes, please create a dedicated branch"

I'm not sure if ~10 commits counted, but thought this may be the way to
go. Once again, thanks for clarifying.

Much appreciated!


p.s. If you'd like a TLDR on that website thread I started I'd happily
attempt one. I just hope you don't find me too presumptions going as far
as I have without having heard your thoughts on it.

  reply	other threads:[~2020-09-03 10:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24  7:28 Are we still in a feature freeze? TEC
2020-09-03 10:30 ` Bastien
2020-09-03 10:37   ` TEC [this message]
2020-09-03 14:54     ` Bastien
2020-09-03 15:24       ` TEC

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=87o8mnxi1t.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --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).