From: Kaushal Modi <kaushal.modi@gmail.com>
To: Adrian Bradd <adrian.bradd@gmail.com>
Cc: Marco Wahl <marcowahlsoft@gmail.com>,
emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Branch "next" garbled
Date: Thu, 11 Oct 2018 23:17:46 -0400 [thread overview]
Message-ID: <CAFyQvY257L9hre4qw9DMfYH9YcbFsNgxNwkfJDvF+zn7wzdvYA@mail.gmail.com> (raw)
In-Reply-To: <87k1mokkg2.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1266 bytes --]
On Thu, Oct 11, 2018, 9:46 PM Adrian Bradd <adrian.bradd@gmail.com> wrote:
>
> Sorry if this is obvious, but what is the next branch
>
Simply put, the next branch is even more bleeding edge than the master.
Bleeding-edgeness: next > master > maint
- maint :: gets published to Org Elpa, etc. Right now the version there is
9.1.x. This branch only takes bug and doc fixes right now
- master :: this is the soon(TM)-to-be released Org 9.2 version. This has
quite a many features (including few breaking) on top of Org 9.1.x. As this
version is planned to be released soon, the plan is to not touch this
branch for the time being as it gets tested out more. Touch this only for
doc and bug fixes for Org 9.2.
- next :: This branch is open to all sorts of commits. Changes here won't
be visible until the next to next major Org release (probably 9.3?).
In general, you would always commit to the most stable branch first and
then merge that to the next less stable branch in succession.
The less stable branch always contains all commits (as-is or merged) from
the more stable branch.
It isn't mentioned on worg in the developers section either
> (https://orgmode.org/worg/dev/index.html).
>
My understanding is that the next branch is not a long term thing.
>
[-- Attachment #2: Type: text/html, Size: 2393 bytes --]
next prev parent reply other threads:[~2018-10-12 3:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 11:45 Branch "next" garbled Marco Wahl
2018-10-03 16:47 ` Nicolas Goaziou
2018-10-03 20:21 ` Marco Wahl
2018-10-12 1:44 ` Adrian Bradd
2018-10-12 3:17 ` Kaushal Modi [this message]
2018-10-03 20:46 ` Uwe Koloska
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=CAFyQvY257L9hre4qw9DMfYH9YcbFsNgxNwkfJDvF+zn7wzdvYA@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=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
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).