|
From: | Adrian Bradd |
Subject: | [O] Purpose of and documentation for the next branch (was: Re: Branch "next" garbled) |
Date: | Thu, 11 Oct 2018 22:02:23 -0400 |
User-agent: | mu4e 0.9.18; emacs 27.0.50 |
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 iton 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 <address@hidden> 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 isduplicated 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
[Prev in Thread] | Current Thread | [Next in Thread] |