From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Sun, 04 Sep 2016 20:42:28 +0200 Subject: [Buildroot] [PATCH 00/16 v3] br2-external: support multiple trees at once (branch yem/multi-br2-external-ID-7) In-Reply-To: (Arnout Vandecappelle's message of "Thu, 1 Sep 2016 23:43:56 +0200") References: <874m611n1e.fsf@dell.be.48ers.dk> <20160831091443.691ffd1c@free-electrons.com> <20160831092643.GA5549@free.fr> Message-ID: <877farwlpn.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Arnout" == Arnout Vandecappelle writes: Hi, > One remark though: we should really document such backward compatibility > issues. I don't think we're currently doing that well. > Where should this be done? > - In CHANGES? At the moment, however, the CHANGES file is not really inviting to > look for that kind of thing. Especially because users will often upgrade in > jumps of 4 or more releases - that makes up 900 lines of CHANGES text... Do you still think this is an issue? It is natually still big, but I do find that readability has improved quite a bit since I removed the Updated/fixed packages list for -rc1. I currently still add it for later rc's, but we could drop that as well if people prefer. > - In the manual? There isn't really an appropriate place for it at the moment. > And how long do we keep it there? > - In some new location? Where? > My personal preference would be in the manual, and keep it for a couple of years. I think we should add it to CHANGES, and add a short notice in the manual that earlier BR versions used a different br2-external setup. -- Venlig hilsen, Peter Korsgaard