January 2019 - xwiki-devs@xwiki.org

[xwiki-devs] [ANN] XWiki 10.11.2 released
by Thomas Mortagne 29 Jan '19

29 Jan '19

The XWiki development team is proud to announce the availability of XWiki 10.11.2. This is a bugfix release that covers important issues that we have discovered since 10.11.1 has been released. You can download it here: https://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.11.2 Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] [Proposal] Roadmap for XS 11.1 & 11.2
by Vincent Massol 25 Jan '19

25 Jan '19

Hi devs, Here’s a proposal for XS 11.1 & 11.2 (already discussed with devs from XWiki SAS). XS 11.1 - February ================= Goals: * Focus on finishing items marked important in 2018 and that couldn't be started Topics: * All: BFD (Priority on Notifications for Guillaume) * STAMP: Vincent (30%) * FASTEN: Vincent (10%) + Thomas (30%) * Simon: Finish "Browsers usually cache JS/CSS resources even if they have changed” (https://jira.xwiki.org/browse/XWIKI-6073) * Simon: Display Reference of documents to copy paste * Marius: Finish autocomplete of references in WYSIWYG Macro parameters (include/display macros, etc) * Marius: ConfigurableClass doesn't support page level configuration case * Marius: Improve the XClass picker when in object edit mode (make it like the Add Macro dialog for WYSIWYG editor) * Thomas: Finish Hibernate upgrade + Performances + Velocity 2.x upgrade Dates: * 11.1RC1: 18th of Feb 2019 * 11.1: 25th of Feb XS 11.2 - March =============== Topics: * STAMP: Vincent(30%) * FASTEN: Vincent (10%) + Thomas (30%) * All: BFD (Priority on Notifications for Guillaume) * Simon: XWIKI-1657: Allow to rename attachments. * Marius: one item from Caty's usability list to select, see https://design.xwiki.org/xwiki/bin/view/Proposal/UsabilitySelection/Usabili… * Thomas: Performances Dates: * 11.2RC1: 18th of March 2019 * 11.2: 25th of March Feedback? Thanks -Vincent

1 1

[xwiki-devs] [VOTE] Drop support for IE11
by Ecaterina Moraru (Valica) 24 Jan '19

24 Jan '19

IE is the last browser we are supporting at a particular version, see http://dev.xwiki.org/xwiki/bin/view/Community/BrowserSupportStrategy . For all the other browsers, we are supporting just the latest release. We are supporting the latest version of Microsoft Edge since XWiki 9.9, starting from 24/Oct/17. Microsoft Edge replaced Internet Explorer as the default web browser since the release of Windows 10 (launched Jul 2015). Internet Explorer 11 is maintained on Windows 10 for compatibility purposes, but is deprecated in favor of Edge and is no longer actively developed. We discussed dropping IE11 in the past Oct 6, 2017 (see https://xwiki.markmail.org/thread/qsrkka6zfrmyxv3d) but the vote failed. Some updated statistics: -------------------------------------------------- XWiki.org's 1 year traffic (between Sep 30, 2016 - Sep 30, 2017) compared to Oct 1, 2017 - May 31, 2018: - Internet Explorer dropped from (5.84%) to (4.65%) -- from this percentage, IE 11 usage has increased from (88.43%) to (88.76%) - Edge increased from (1.56%) to (1.84%). In terms of Worldwide market share for Desktops, for the past 12 months (according to http://gs.statcounter.com/browser-market-share/desktop/ ), we have Sep, 2016 - Sep, 2017 compared to May 2017 - May 2018: - Internet Explorer dropped from 8.21% to 6.97% - Edge dropped from 4.3% to 4.15% In May 2018, Global Market Share Worldwide for All Platforms contains: - Chrome 58.09% - Safari 13.78% - UC Browser 8.16% - Firefox 5.27% - Opera 3.68% - Internet Explorer combined is at 3.08% (with IE 11 having 2.65%. IE11 in August 2017 had 3.04%) - Edge combined having 1.91% (Edge combined in August 2017 had 1.8%) - etc. -------------------------------------------------- In terms of statistics, IE11 is more used than Microsoft Edge. The only argument of dropping IE11 is that it's a browser that is deprecated for about 3 years, and it's limiting the usage of newer specifications (like CSS Flex, Grid, etc.) I'm curios about how this period of supporting both IE11 and Edge went, and if you have other examples of things you wanted to use and are not supported by IE11. Thanks, Caty

3 4

[xwiki-devs] [Proposal] Document picker in include and display macros
by Adel Atallah 23 Jan '19

23 Jan '19

Hi devs, After discussing with Marius and Thomas, we thought it might be a good idea to do the following to have a document picker in the include and display maros: * Remove the deprecation of the document parameter (only for the include macro). * Introduce a new annotation to macro parameters to specify / override its type (different from its actual java type). The new annotation will mostly be useful for the WYSIWYG side. In our case we want to use the document parameter which is a String. The annotation will allow us to work with a DocumentReference instead which can be used to display the document picker when editing the macro in WYSIWYG mode. To be clear, here is how we would use it: @PropertyType(DocumentReference.class) public void setDocument(String document) WDYT? Thanks, Adel

4 12

[xwiki-devs] MyXWiki.org legal information
by Ecaterina Moraru (Valica) 23 Jan '19

23 Jan '19

Hi Devs, We had an user ask about MyXWiki.org privacy agreements, see https://forum.xwiki.org/t/agreement-on-wiki-at-myxwiki-org-privacy/4241 I've added more details on MyXWiki.org homepage about: * Who is the legal entity behind MyXWiki? * What about Copyright and Intellectual Property? * What about Privacy Policy? See https://www.myxwiki.org/xwiki/bin/view/Main/ Please review it, see if you have more adjustments / details. Thanks, Caty

3 3

[xwiki-devs] [Proposal] Change of XS Cycle strategy to account for Christmas
by Vincent Massol 20 Jan '19

20 Jan '19

Hi devs, Some devs mentioned it’s too hard to release the N.11 release since it happens around Christmas every year. Here’s a proposal: * Shorten the cycle to 11 releases instead of 12. * Release N.9 at end of Nov * Release N.10 at end of first week of Jan. Note: N.10RC1 would be released mid December (about 17th of Dec to have 3 weeks of RC). * Release N+1.0 at end of February. Start of N+1.0 work Pros: * No release during Christmas, yeah :) * More time to prepare the first LTS bugfix release, i.e. N.10.1, which can be done during the month of January. * More time for the first released of N+1 (i.e. N+1.0). This is important since that’s the release where we can do heavy refactoring and it’s not bad to get some more time. Cons: * One less release WDYT? Do you see other cons? Thanks -Vincent

7 15

[xwiki-devs] [XWiki Day] BFD#204
by Oana-Lavinia Florean 18 Jan '19

18 Jan '19

Hello devs, This Thursday is BFD#204: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingday Our current status is: * -31 bugs over 120 days (4 months), i.e. we need to close 31 bugs to have created bugs == closed bugs * -137 bugs over 365 days (1 year) * -147 bugs over 500 days (between 1 and 2 years) * -340 bugs over 1600 days (4.3 years) See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#204 dashboard to follow the progress during the day: https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=14356 Good luck at fixing bugs, Lavinia

1 1

[xwiki-devs] [proposal] Don't rely on depth anymore for HeadingLevelSplittingCriterion
by Simon Urli 15 Jan '19

15 Jan '19

Hi everyone, I'm working on the document splitter in order to fix the following issue: https://jira.xwiki.org/browse/XWIKI-13100 However I noticed that the current implementation of the document splitter relies on the XDOM depth. That means if an user wants to split a document with header level 1, the header blocks have to be under the root of the document, they cannot be under a GroupBlocks, or as it's the case in XWIKI-13100, under a NumberedListBlock. Moreover, currently we do not rely at all on the header block level for the splitting: if you have a header level 2 under the root and you decided to split the document with header level 1, it will be splitted since only the document depth is used. So I propose to change this behaviour and to rely on HeaderBlock header level *only* for the splitting criteria: the depth won't be used anymore. In practice I propose to keep the API of SplittingCriterion which defines the method with depth parameter, but to not rely on this parameter in the HeadingLevelSplittingCriterion implementation, that we rely on for splitting imported office document. WDYT? Simon -- Simon Urli Software Engineer at XWiki SAS simon.urli(a)xwiki.com More about us at http://www.xwiki.com

1 0

[xwiki-devs] [ANN] XWiki 10.11.1 released
by Adel Atallah 15 Jan '19

15 Jan '19

The XWiki development team is proud to announce the availability of XWiki 10.11.1. This is a bugfix release that covers important issues that we have discovered since 10.11 has been released. Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.11.1 Thanks for your support -The XWiki dev team

1 0

[xwiki-devs] [XWiki Day] BFD#203
by Oana-Lavinia Florean 11 Jan '19

11 Jan '19

Hello devs, This Thursday is BFD#203: http://dev.xwiki.org/xwiki/bin/view/Community/XWikiDays#HBugfixingday Our current status is: * -29 bugs over 120 days (4 months), i.e. we need to close 29 bugs to have created bugs == closed bugs * -130 bugs over 365 days (1 year) * -46 bugs over 500 days (between 1 and 2 years) * -353 bugs over 1600 days (4.3 years) See https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=10352 Here's the BFD#203 dashboard to follow the progress during the day: https://jira.xwiki.org/secure/Dashboard.jspa?selectPageId=14352 Good luck at fixing bugs, Lavinia

1 1