+1 Thanks, Marius On Tue, Apr 10, 2012 at 7:21 PM, Vincent Massol <vincent(a)massol.net> wrote:

On Apr 10, 2012, at 6:21 PM, Vincent Massol wrote: I'm having second thoughts about this item. All the other items are fine but this one is a bit harsh IMO. Imagine what will happen: users will download latest version, will try to install extensions and they'll fail badly with huge stack traces… (simply because most if not all of extensions not done by the XWiki dev team will contain deprecated calls). Thus, without any warnings, users will find a "non working XWiki", which is very bad both for the user and for XWiki's image. We want users to find XWiki to be a rock solid solution. Thus what I think would be better: * Step 0 (now): Keep releasing a distribution with legacy modules by default for the moment * Step 1: Work on our Wiki Console, i.e. the ability for people editing pages to see inside the wiki the places where they call deprecated apis. Also have a page somewhere listing all deprecated made throughout the wiki. Basically work on showing deprecated apis to users so that they **know** about them and can fix them. This is the first step in the awareness. * Step 1 bis: Work on providing a nice error message when a page calls a deprecated API that is not available in the wiki, explaining to the user how to contact his admin and how to install the legacy module required (even better, use the EM to install it at the click of a button). * Step 3: Provide a distribution without legacy modules. A second step could be to make that distribution the default but still make the legacy distribution visible so that it's easy for users to use it if they need to use extensions that use deprecated calls for example WDYT? Of course this strategy would need to be refined but the general gist is that we should still provide legacy modules till we've improved our way of showing, fixing and handling deprecated calls from wiki pages. Thanks -Vincent