Hi Sergiu, On Sep 12, 2013, at 5:11 PM, Sergiu Dumitriu <ser...@xwiki.com> wrote:
> On 09/11/2013 05:58 AM, Guillaume "Louis-Marie" Delhumeau wrote: >> Since Enterprise embeds Workspaces by default since 5.2-m2, I think it does >> not make any sense to release XWiki Manager (XEM) anymore. >> >> The build is currently broken (because of the XAR organization changes). >> >> So I propose to remove XWiki Manager: >> - stop releasing it >> - move the github repo to xwiki-contrib/retired >> - update manager.xwiki.org to explain the changes in XWiki 5.2. >> - move the manager jira to the retired category >> - remove the build in ci.xwiki.org >> >> Here is my non-binding +1. >> >> LM > > -1. This is very premature, the new workspaces haven't been available > for a long enough time to be sure it is a good replacement for XEM. We will never be able to support XEM as it was since we've modified workspaces (we didn't add a new module ;)). Also, since XEM has always been a packaging only it's not a bit deal. You could always install the XEM feature on an XE. > Do workspaces fulfill all the needs of existing XEM users? yes it's the same thing... > Does the new implementation offer support for the Farm usage? same as XEM but the UI module is not installed (it was installed in XEM but hidden). We could add it but it's a bad idea since it's misleading. The better solution is what we plan for 5.3 which is to merge the 2 notions. > Is there a clear migration path? Manual or automatic? automatic, there's a jira issue for making it work in 5.2. > Is the new wiki management UI going to be at least as easy to use as the > old one? What's the learning curve for administrators? it's the same one… > If the build is broken, it's easier to fix it than to upset a large > userbase. No. Again, we modified workspaces so even if continue providing the XEM packaging the changes will be there and if we upset users in XE we will upset them in XEM... > Why do we insist so much on maintaining backwards > compatibility for Java APIs that we're almost certain nobody uses, yet > we're OK with dropping an entire product without a proven alternative, > hoping that in one or two more releases that alternative will actually > be fully implemented? See above. Thanks -Vincent _______________________________________________ devs mailing list devs@xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
