emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Adrian Bradd <adrian.bradd@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Marco Wahl <marcowahlsoft@gmail.com>, emacs-orgmode@gnu.org
Subject: Purpose of and documentation for the next branch (was: Re: Branch "next" garbled)
Date: Thu, 11 Oct 2018 22:02:23 -0400	[thread overview]
Message-ID: <87in27ly6o.fsf@gmail.com> (raw)


Not 5 minutes later did I find this in another thread:

>> Also, I'd like to avoid making changes to "master" branch. It 
>> should be
>> considered frozen while we're waiting for Org 9.2. Please 
>> install next
>> new features (that one is OK, I guess) in "next" branch, and 
>> rebase it
>> on top of "master".

So the next branch is a temporary replacement for master while 
master is frozen awaiting a release?

> It might be worth the effort to document the role of the "next" 
> branch somewhere.

Perhaps on the worg developer page?

Adrian Bradd <adrian.bradd@gmail.com> writes:

> Hi all,
>
>> To prevent further complications with this branch, I suggest to 
>> treat is
>> like master and master like maint. I.e., every commit done in 
>> master is
>> duplicated into next so that final merge is easier.
>
> Sorry if this is obvious, but what is the next branch?
>
> This is the first I have heard of it (not that my org-fu is all 
> that comprehensive). I took a look around but I couldn't find 
> any 
> details about it in the mail archives. Granted I wasn't 
> expecting 
> much from a search that included the phrase "next branch". It 
> isn't mentioned on worg in the developers section either 
> (https://orgmode.org/worg/dev/index.html).
>
> Cheers,

Cheers,

-- 
Adrian Bradd

next             reply	other threads:[~2018-10-12  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-12  2:02 Adrian Bradd [this message]
2018-10-12  9:24 ` Purpose of and documentation for the next branch Nicolas Goaziou

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=87in27ly6o.fsf@gmail.com \
    --to=adrian.bradd@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=marcowahlsoft@gmail.com \
    /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 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).