Re: 2.4.x and 2.6.x ... next steps
On 12 Sep 2018, at 15:39, William A Rowe Jr <wrowe@xxxxxxxxxxxxx> wrote:
> Now, why would we *need* a 2.5.x branch?
The primary need is to remove stuff that we deem not-ready-for-2.6-yet. Modules without any docs for example would need to be either documented or removed-from-2.5-that-will-become-2.6, keeping trunk as it is.
We don’t want to remove work from trunk that needs polishing for the reasons you’ve already described.