[xwiki-devs] Stabilization of XE 3.3 final - Help needed
Hi devs, We're having a hard time stabilizing XE 3.3 and here's the list of outstanding issues that we need fixed before we can release 3.3 final: 1. Fix the issues we have when upgrading xwiki.org to 3.3. It seems it's a memory leak somewhere. 2. Make it work on Oracle. Several users have complained that it's not working fine on Oracle. 3. We need to have the Extension Manager working and for that we need the Extension Repository working on extensions.xwiki.org and for that we need 1 fixed. 4. Ensure the new XEM works fine. Sorin has had issues using it in the past 2 days so we need to ensure it's ready and real easy to use. 5. Fix failing tests in our test suite: http://ci.xwiki.org/ We need all devs to stop working on new stuff and to focus on helping fix those issues for the final. We should not do any more commits that are not bug fixes on master too. I'm working on point 1 today (anyone who wants to help is welcome too of course). Who can work on the other points? Thanks -Vincent
On Wed, Nov 30, 2011 at 10:43 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
We're having a hard time stabilizing XE 3.3 and here's the list of outstanding issues that we need fixed before we can release 3.3 final:
1. Fix the issues we have when upgrading xwiki.org to 3.3. It seems it's a memory leak somewhere. 2. Make it work on Oracle. Several users have complained that it's not working fine on Oracle. 3. We need to have the Extension Manager working and for that we need the Extension Repository working on extensions.xwiki.org and for that we need 1 fixed. 4. Ensure the new XEM works fine. Sorin has had issues using it in the past 2 days so we need to ensure it's ready and real easy to use.
I am testing XEM/Workspaces today.Now the installation is pretty stable, but we have a major performance issue when creating a new Workspace because of some translations taking very long during import. Eduard is aware of that, and I hope it will be fixed until 3.3 final. Meanwhile I will continue testing Workspaces and report all issues on JIRA. 5. Fix failing tests in our test suite: http://ci.xwiki.org/
We need all devs to stop working on new stuff and to focus on helping fix those issues for the final.
We should not do any more commits that are not bug fixes on master too.
I'm working on point 1 today (anyone who wants to help is welcome too of course).
Who can work on the other points?
Thanks -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Regards, Sorin B.
Hi, On Wed, Nov 30, 2011 at 12:50 PM, Sorin Burjan <[email protected]>wrote:
On Wed, Nov 30, 2011 at 10:43 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
We're having a hard time stabilizing XE 3.3 and here's the list of outstanding issues that we need fixed before we can release 3.3 final:
1. Fix the issues we have when upgrading xwiki.org to 3.3. It seems it's a memory leak somewhere. 2. Make it work on Oracle. Several users have complained that it's not working fine on Oracle. 3. We need to have the Extension Manager working and for that we need the Extension Repository working on extensions.xwiki.org and for that we need 1 fixed. 4. Ensure the new XEM works fine. Sorin has had issues using it in the past 2 days so we need to ensure it's ready and real easy to use.
I am testing XEM/Workspaces today.Now the installation is pretty stable, but we have a major performance issue when creating a new Workspace because of some translations taking very long during import. Eduard is aware of that, and I hope it will be fixed until 3.3 final. Meanwhile I will continue testing Workspaces and report all issues on JIRA.
Regarding the missing translation messages at import time, I don`t think that there is much I can do about it. XWiki gets to import the page XWiki.XWikiPreferences (that has registered as translation bundle page X.Y) before page X.Y gets to be imported. Between XWiki.XWikiPreferencesand X.Y, you will get warnings that X.Y is not found. After X.Y gets imported as well, the warnings go away. This is how the import works and it does not have any transactional-like properties. The warnings could have an impact on performance, but I don`t think it would be considerable. Regarding general performance, again, it's not related to workspaces. It has the same performance as creating a new subwiki by using a template (which is what actually happens in the background). It is as fast as before. Even so, I will try to have a look and identify some possible bottlenecks. Of course, help is appreciated :) Thanks, Eduard
5. Fix failing tests in our test suite: http://ci.xwiki.org/
We need all devs to stop working on new stuff and to focus on helping fix those issues for the final.
We should not do any more commits that are not bug fixes on master too.
I'm working on point 1 today (anyone who wants to help is welcome too of course).
Who can work on the other points?
Thanks -Vincent _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
Regards, Sorin B. _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
participants (3)
-
Eduard Moraru -
Sorin Burjan -
Vincent Massol