> On 22 May 2017, at 15:34, Thomas Mortagne <[email protected]> wrote: > > I would be more in favor of moving them to some extension than can be > easily installed if really needed.
The downside with this approach compared to the legacy approach are: * The user will gets broken before they can understand the problem and fix it so bad from a usability POV. They’ll also need to understand where to get the extension and install it * We break a contract if we consider that default pages are a contract (we need to decide about that but I think it would be fair to say the pages are a contract) Thanks -Vincent > On Mon, May 22, 2017 at 2:41 PM, Vincent Massol <[email protected]> wrote: >> Hi devs, >> >> We have this jira issue I created a while ago and I’d like to move forward: >> https://jira.xwiki.org/browse/XWIKI-13101 >> >> I have one question: >> Should we move the 4 pages into a legacy module in platform and bundle it in >> XE or just remove them? >> >> My POV: >> We could consider the pages as APIs I guess and use the API strategy of >> moving deprecated APIs to legacy. >> >> WDYT? >> >> Thanks >> -Vincent > > > > -- > Thomas Mortagne
