xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] Plenty of JIRA issues with missing "affects" field...

by Vincent Massol

Hi devs, I've fixed a few of those but there are still plenty. If you feel like helping, feel free to add affects to them (and "components" where it's missing): http://jira.xwiki.org/issues/?jql=category%20%3D%2010000%20AND%20affectedVe… Thanks -Vincent

11 years, 10 months

[xwiki-devs] [Proposal] XWiki memory requirements increase...

by Vincent Massol

Hi devs, Right now we recommend this on http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Installation#HPrerequis… : "A minimum of 300MB of heap memory and 96MB of permGen. Recommended values are above 512MB for the heap and 128MB for the permGen (-Xmx512m -XX:MaxPermSize=128m)" I've discovered on http://ci.xwiki.org/job/xwiki-enterprise-test-extension/org.xwiki.enterpris… that we had an OOM and it seems to happen more and in more in our functional tests on CI. Something we've done must have increased our permgen memory. I've done some measurements with yourkit and here's what I found: * After XWiki is started and before any page is called we already use 64MB of permgen * After calling the home page, the permgen used goes to 101MB * After calling a page using the code macro, the permgen goes to 132MB So it seems that your default value of 96MB and recommended value of 128MB are not enough… BTW forcing garbage collection reduces from 132MB to 130MB (not much). We need to either find what is taking all our permgen memory or if it's legit increase our recommendations and the default value we use in start_xwiki.sh/bat Any idea? My hunch tells me the Extension Manager could be the cause. Thanks -Vincent

11 years, 10 months

[xwiki-devs] [Notice] Dashboard link in release notes

by Vincent Massol

Hi devs, I've modified the release notes template on xwiki.org so that we always put a link to the jira dashboard in all our release notes from now on. Examples: - http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki451 - http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki50M1 It's up to the RM to create the associated JIRA dashboard and filters (or anyone who wants to help for that matter but it's up to the RM to make sure it's there). Thanks -Vincent

11 years, 10 months

[xwiki-devs] [Proposal] Roadmap for XWiki 5.0

by Vincent Massol

Hi devs, With XWiki 4.x cycle coming to an end soon, it's time to prepare the roadmap for XWiki 5.0. This is a proposal that comes from some internal meetings done with XWiki committers who are working for XWiki SAS. If you're interesting in participating to this release, don't hesitate to add yourself to the list so that everyone can have some visibility of what's going to be worked on during this timeframe! If you think some work defined below doesn't go in the interest of the project also feel free to raise issues. Features: * Continue SOLR implementation - Edy * EM upgrade of subwikis + flavor concept (add Flavor type in EM/Repository) + leftover from 4.x for EM/DW - Thomas + Marius for DW UI part for flavors * AWM work from 4.x to finish (see http://www.xwiki.org/xwiki/bin/view/Roadmaps/WebHome) - Marius * scalable import/export - Thomas * Home page improvements (XE) and usability improvements in general - JV * Horizontal Menu management (add, remove pages) - JV * virtual=1 by default - Edy (Edy will need to make a proposal for that since it's an important decision ;)) * l10n speed improvements - Ludovic Important JIRAs sorted by priority (most important first): * AWM Add the ability to publish an application as an extension XWIKI-7377 - Marius * AWM Add the ability to export an application XWIKI-7376 - Marius * Unable to edit a page using the WYGIWYG editor after adding a dashboard macro to it XWIKI-8495 - Need volunteer * Improve AWM for it to deal with error messages made by Client when filling the AWM form in using special chars XWIKI-8763 - Marius * Import of Office file breaks Activity Stream and Recently Modified Panel XRENDERING-261 - Need volunteer * Cannot change document title from "inline" mode XWIKI-7905 - Not sure if we want it, to be checked with Marius * When the workspace owner is changed, the new owner is not added as a member nor in the admin group XWIKI-8397 - Edy * Unable to upload a new attachment using the "All pages" tab in the WYSIWYG editor XWIKI-8465 - Marius * Workspace owner and initial members not set as members (nor in admin group) when the workspace identifier contains an underscore XWIKI-8394 - Edy Investigations: * XEM Homepage / Portal - Caty * Knowledge base Flavor - Caty/Ludovic * New Activity Stream Investigation Part 1 - JV (he's agree to become our AS champion :)) * General Flavours Investigation - Caty + input from tech Regarding dates I'm proposing the following: * 5.0M1: 4 March 2013 * 5.0M2: 25 March 2013 * 5.0RC1: 8 April 2013 * 5.0Final: 15 April 2013 Thanks -Vincent

11 years, 10 months

[xwiki-devs] [ANN] XWiki 4.5.1 released

by Vincent Massol

The XWiki development team is proud to announce the availability of XWiki 4.5.1. This is a bugfix release. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki451 Thanks -The XWiki dev team

11 years, 10 months

[xwiki-devs] [Notice] BFD#10

by Vincent Massol

Hi devs, Tomorrow is BFD#10: http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HXWikiDa… We currently have 871 bugs fixed out of 908 created for the last 360 days: http://jira.xwiki.org/secure/Dashboard.jspa#Created-vs-Resolved-Chart/10470 We closed 19 bugs last Thursday: http://www.xwiki.org/xwiki/bin/view/Main/Bug+Fixing+Day+9 Let's see if we can do as well tomorrow! We "just" need to fix 37 bugs to be back in the green. Please join us in the bug hunt tomorrow :) Thanks -Vincent

11 years, 10 months

[xwiki-devs] [Proposal] Provide UI extension points in the current set of templates

by Jean-Vincent Drean

Hi, in 4.x we introduced UI Extensions (UIX) and "Extension Points", it allows applications to come and plug their bits of UI where it is possible [1]. 5.x is a good time to provide a list of useful Extension Points (UIXP) in our velocity templates, allowing applications to plug themselves in, for example : the header, before the content, the footer, etc. To allow this I can think of 2 strategies: == 1) Manually add UIXPs == Actions: * Discuss where are the common places where applications would like to plug (in our opinion) * Make a lengthy list * Vote it * Introduce an API call (services.uix.getExtensions()) for each item in the list * Commit it Pros: * We can carefully build the UI API Cons: * We can't think of everything * Long process * Overridden templates won't display the extensions == 2) Instrument our templating mechanism with UIXPs == Actions: * Modify the #template macro so that it create UIXPs before and after the parseTemplate call. Calling #template.vm would create the following UIXP: ** platform.template.global.before (or: platform.template.global.above, platform.template.global.top) ** platform.template.global.after (or: platform.template.global.below, platform.template.global.bottom) * Commit it Pros: * A lot of available UIXPs * We've worked on our template architecture for a long time, UIXP would benefit from that * Quick process Cons: * It'd make our current template architecture an API ... but since templates can be overridden in skins, it already is one. * A lot of API calls (but tests with YourKit shows that it doesn't impact performance) Note: 2) doesn't exclude 1), we'd probably still need to introduce UIXP within templates, but we'd have way less UIX API calls with this method. WDYT ? I guess it's quite obvious that my opinion is biased, I've started playing with 2) and it's quite cool :) [1] http://extensions.xwiki.org/xwiki/bin/view/Extension/UIExtension+Module Thanks, JV.

11 years, 10 months

[xwiki-devs] (no subject)

by 綦玉冰

11 years, 10 months

[xwiki-devs] [PROPOSAL] Change default resolver to used in model ScriptService

by Thomas Mortagne

Hi devs, Right now the model script service use "currentmixed" as default resolver and it should use "current" one IMO: 1) it's behavior is not very clear for a newcomer 2) it's pretty much unusable for attachments The difference between the two resolver is that "currentmixed" resolve document name beased on default (WebHome) instead of current document. AFAIK this resolver as been introduced for retro compatibility purpose because in some old APIs like XWikiDocument contructors the document name was resolver as WebHome and not based on the current document. So I propose to change the default resolver to "current". Here is my +1. This script service is not much used yet, I doubt anybody is using it expecting to get WebHome when resolving the document name but since it's a behaviour change 5.0 is the right time for it. -- Thomas Mortagne

11 years, 10 months

[xwiki-devs] [Contrib] Load Test Application

by Sorin Burjan

Hello everybody, I am building a small application to perform load test in XWiki. I have exported several spaces from xwiki.org used to generate the content, and cleaned them a little bit to suit my needs. I would like to request a repository on Contrib so I can commit the content needed for generation but also the scripts that will generate the content needed for testing. I was thinking of application-loadtest. Thanks, Sorin B.

11 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs