I am not saying that it would be a non issue I am just suggesting that it would make more work all round for both extension developers and the Extension team - and why should it be a "minor" release? I would suggest that the ACP redesign is a major release in its own right.hanakin wrote: Wed Oct 04, 2017 3:29 am well also if it all happened in at once and to include a re-design as well i doubt we would want to release it under the guise of a minor release which would be from your perspective a non-issue in that case.
The point that I am trying to get over is that at a rough guess about 80+% of extensions will be affected by an ACP style change unless, at least initially, there is backward compatibility. Also if the structure of the ACP is changed then there will be quite a few extensions affected - so I would suggest that, again initially, that the module structure is not changed even though some aspects of it may not be used/needed.
Don't get me wrong here I fully agree that the ACP can at times be difficult to navigate (I sometimes spend ages trying to find little used options!) and that it is long overdue not only a style "makeover" but a general reorganisation - I am just trying to draw attention to the fact that extensions will be affected by this and that some consideration is given to the overall process of updating the ACP.