From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adrian Bradd Subject: Purpose of and documentation for the next branch (was: Re: Branch "next" garbled) Date: Thu, 11 Oct 2018 22:02:23 -0400 Message-ID: <87in27ly6o.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50747) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gAmmh-0002zg-5q for emacs-orgmode@gnu.org; Thu, 11 Oct 2018 22:02:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gAmmd-0004Ua-VH for emacs-orgmode@gnu.org; Thu, 11 Oct 2018 22:02:35 -0400 Received: from mail-qt1-x830.google.com ([2607:f8b0:4864:20::830]:43789) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gAmmZ-0004Rp-5g for emacs-orgmode@gnu.org; Thu, 11 Oct 2018 22:02:28 -0400 Received: by mail-qt1-x830.google.com with SMTP id q41-v6so12293460qtq.10 for ; Thu, 11 Oct 2018 19:02:26 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Nicolas Goaziou Cc: Marco Wahl , emacs-orgmode@gnu.org 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 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