- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [Proposal] Let contrib committers be JIRA administrators for contrib projects?

by Vincent Massol

Hi devs, Stephane Lauriere was asking us to have admin rights for the chartjs contrib project so that he could do a release. Right now only the owner + global jira admins have admin rights. I’m proposing to change the current Administrator role for JIRA Contrib Projets from: * jira-administrators to: * jira-administrators * contrib-committers * xwiki-committers WDYT? Thanks -Vincent

6 years, 9 months

3
5
0 0

[xwiki-devs] [XWiki Day] BFD#200

by Oana-Lavinia Florean

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

6 years, 9 months

1
1
0 0

[xwiki-devs] [Proposal] Add a new xwiki/xwiki-jenkins-slave repository

by Vincent Massol

Hi devs, In order to have ci.xwiki.org use docker-based agents (i.e. master will spawn agents using a pre-built docker image), I need to create a github repository to hold the Dockerfile for that docker image, and so that the xwiki dockerhub organization can have an automated build to build it regularly. I’m thus proposing to create a new "xwiki-jenkins-slave” repository in the xwiki github org. Since I’m working on this now, I’ll go ahead and create the repo and I can remove it if someone disagrees. Thanks -Vincent

6 years, 9 months

1
0
0 0

[xwiki-devs] [ANN] XWiki 10.8.2 Released

by Clément Aubin

Hi everyone, The XWiki development team is proud to announce the availability of XWiki 10.8.2. This is a bugfix release that covers important issues that we have discovered since 10.8.1 [1] has been released. See the release notes [2] for more information. Thanks, and have a great end of week, Clément [1] https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.8.1/ [2] https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.8.2/

6 years, 9 months

1
0
0 0

[xwiki-devs] [XWiki Day] BFD#199

by Oana-Lavinia Florean

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

6 years, 9 months

1
1
0 0

[xwiki-devs] [Proposal] New xwiki-clover-maven repository

by Vincent Massol

Hi devs, I’d like to refactor the groovy code that I’ve currently put at https://github.com/xwiki/xwiki-jenkins-pipeline/blob/59051fd8f61bd5a65db790… and to move it into an XWiki Maven plugin for Clover. The goal of this plugin is to take as input two clover.xml Clover data files and to generate a diff report (example: http://maven.xwiki.org/site/clover/20181120/XWikiReport-20171222-1835-20181…). Rationale for move this outside of Jenkins: * Less dependency on Jenkins * Much easier to test * Better versioning and release * Increased reuse (any project in the world will be able to use it whereas the pipeline is specific to xwiki and not reusable easily) It’s not linked to releases of XWiki. But it should be maintained by the xwiki dev team since we use it in our pipeline to compute the global coverage and generate reports/emails when global TPC is lowered. WDYT? Thanks -Vincent

6 years, 9 months

3
2
0 0

[xwiki-devs] [ANN] XWiki 10.10 released

by Alex Cotiugă

Hello all, The XWiki development team is proud to announce the availability of XWiki 10.10. In this version, a new protection helper was introduced to prevent users from breaking the wiki when an XClass page is being refactored, PDF export looks better now and the new auto-suggestion feature starts to be enabled in some places. It's now possible to easily enable asynchronous execution and caching for panels, wiki UI extensions and wiki macros, this making the rendering of the page faster. Among other things, Wiki Macros can now have typed parameters and it is now possible to make the content of a macro editable inline with the WYSIWYG editor. 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.10/ Thanks for your support -The XWiki dev team

6 years, 9 months

2
1
0 0

[xwiki-devs] Postpone of XWiki 10.10

by Alex Cotiugă

Hello devs, There are some issues in progress for 10.10 release + some testing for them so I propose to postpone the release for tomorrow. Thanks, Alex

6 years, 9 months

1
0
0 0

[xwiki-devs] [Proposal] WCAG exception: consecutive line breaks

by Simon Urli

Hi everyone, one of the most validation error we have with WCAG is about consecutive line breaks: basically a presents in a page. This happens mostly in our translation pages since the linebreaks in plain syntax are translated in tags. Caty provided a lot of details about this error on the related issue: https://jira.xwiki.org/browse/XWIKI-15666. Currently we have around 140 validations failure because of this. Different proposal have been made in order to fix it, that I will try to sum-up here: A. Remove completely this validation check B. Add an exception for the translation pages C. Triggers the error only if more than 2 consecutive breaks is encountered D. Create a rendering syntax dedicated to translation pages A. Remove completely the validation check pros: * the easiest one * apparently the rule is not checked in other accessibility test, so its real purpose for accessibility is unclear cons: * IMO this rule is useful for checking the good practice of not using B. Add an exception for the translation pages pros: * same as for A cons: * ? C. Triggers the error only if more than 2 consecutive breaks is encountered pros: * ? cons: * we would miss some consecutive that are used only for style and we would catch some others in translations if we do 3 linebreaks instead of 2. IMO it's only moving the problem D. Create a rendering syntax dedicated to translation pages pros: * remove completely the problem of consecutive in translations * can maybe be used to present them in another way? cons: * need to develop/test/maintain a new rendering syntax I'd personnaly vote like this: A: +0 B: +1 C: -1 D: +0 WDYT? Simon -- Simon Urli Software Engineer at XWiki SAS simon.urli(a)xwiki.com More about us at http://www.xwiki.com

6 years, 9 months

6
7
0 0

[xwiki-devs] [XWiki Day] BFD#198

by Oana-Lavinia Florean

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

6 years, 9 months

1
1
0 0

[xwiki-devs] [ANN] XWiki 10.10-rc-1 released

by Guillaume Delhumeau

The XWiki development team is proud to announce the availability of XWiki 10.10-rc-1. For users, this version brings a protection when a page containing an XClass is moved or renamed. By default, the PDF export looks better now. In addition, the recent auto-suggestion feature has been enabled in a few places. For developers, a new asynchronous framework has been created. It allows the execution of desired parts of the rendering of a page to be executed asynchronously, with an AJAX request. This makes the rendering of the page faster, making the least important parts visible after the page is loaded. Among other things, Wiki Macros can now have typed parameters and it is now possible to make the content of a macro editable inline with the WYSIWYG editor. To finish, more than 30 bugs have been fixed since XWiki 10.9. 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.10RC1/ Thanks for your support -The XWiki dev team

6 years, 9 months

2
2
0 0

[xwiki-devs] [Proposal] Roadmap for XS 10.11

by Vincent Massol

Hi devs, Here’s a roadmap for XS 10.11 which is the last release of the 10.x cycle/year. Goal: Mostly stabilization release (bug fixing and last moment polishing of features introduced in the 10.x cycle) * All: BFD (20%) * Thomas/Vincent: Improve STAMP KPIs (20%) * All: Bug fixing/small polishing focus on items added during 10.x * Marius/Adel: Auto complete of references in WYSIWYG Macro Dialog (+ grouping feature so that users don't get both "page" and "reference" at the same time + "deprecated"/"priority" to show "page" more proeminently than "reference") * Thomas: More async/caching of UIX. * Thomas: Bug: https://jira.xwiki.org/browse/XWIKI-14635 : Unsupported character exception is warned in console when downloading attachment Dates: * 10.11RC1: 17th of Dec 2018 * 10.11Final: 24th-31st of Dec 2018 (I’m putting a range since it’s Christmas and we don’t know who’ll be there) Let me know if you have remarks/questions. Thank you -Vincent

6 years, 9 months

1
3
0 0

[xwiki-devs] [Proposal] Jobs for the multiple configuration testing

by Vincent Massol

Hi devs, I’m still not sure but FTM I was thinking of having 2 pipeline jobs: 1) Job 1: Execute one functional test only (e.g. MenuIT for now) but on the maximum number of configurations, in order to flesh out configs that don’t start properly. For example XWiki on Tomcat 9.x would fail (since the Tomcat 9.x docker image uses java9+). The job would not send a mail on failure but it would update a report page (could even update a page on xwiki.org directly or if too complex update some page on maven.xwiki.org somewhere). This job would run not very often but say once per week. Note that one config takes 3-4 minutes to run, so 50 configs would take 3 hours which is acceptable. 2) Job 2: Execute all functional tests on a subset of supported configs. For example we don’t need to run all the tests on PostgreSQL/Jetty/Chrome if we already run on PostgreSQL/Tomcat/FF and MySQL/Tomcat/Chrome. This job will take a long time to execute. We’ll start with 3-4 configs and will go to about 10 configs when we add more. The tests will take roughly 2 hours to execute per config I think. So a total of 20 hours when we have 10 configs. If we run those once per week it should be fine. Note: Once we have job 1 & 2, we won't need to have the smoke tests I add as part of the platform JenkinsFile. WDYT? Thanks -Vincent

6 years, 9 months

5
10
0 0

[xwiki-devs] [Proposal] Always add a link to the reference doc in the RN items

by Vincent Massol

Hi devs, This is something I mentioned a few times (just did on IRC/matrix an hour ago too) but I don’t know if we have an agreement about to, so I’m making a proposal. The idea is that I think it would be nice for users to be able to the read the RN and for each item to be able to navigate to the reference documentation to know more about the topic. Thus the proposal is to always add a link to the reference doc in RN items. For example I added a link here: https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/10.10RC1/#HAll… When I created the RN app I had hesitate to have a field for that but I thought it be nicer if the links were in the text (better flow) and it would take less visual space (if we have a field we’ll need to add the info somewhere which will take more space). The downside is that everyone is forgetting to do it and it's not enforceable automatically. WDYT? Thanks -Vincent

6 years, 9 months

6
5
0 0

[xwiki-devs] Postpone of XWiki 10.10-rc-1

by Guillaume Delhumeau

Hello. To let Marius finish his work, I propose to postpone the release of XWiki 10.10-rc-1 to tomorow. Thanks, -- Guillaume Delhumeau (guillaume.delhumeau(a)xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project

6 years, 9 months

1
0
0 0

[xwiki-devs] Slightly improved default pdf export look and feel

by Anca Luca

Hello devs, I've whipped up quickly a couple of changes to the default PDF export of the XWiki platform, to try to make it look a little nicer. I created the issue here https://jira.xwiki.org/browse/XWIKI-15761 and the pull request here https://github.com/xwiki/xwiki-platform/pull/900 . I would like to merge that into master unless somebody has something against it, so please speak up now. Longer story: I know that "nicer" is a subjective term, and that a lot more can be done to improve this default PDF export. My idea was that the current defaults we have (for the font family, for example, or the information we display in the pdf header/footer and the style associated) are not the result of an actual studied choice, iirc they are just defaults that were set like that in the first version of that export and never changed. Thus, I don't see why we couldn't slightly change these defaults (without changing the information displayed or risking regressions) to have a slightly better looking default PDF, while still allowing all customizations just they way they worked before. These modifications are not blocking nor replacing in any way the more serious improvements that can be done on the PDF export, they're just slightly improving the current defaults. Best regards, Anca

6 years, 9 months

2
7
0 0

[xwiki-devs] [XWiki Day] BFD#197

by Oana-Lavinia Florean

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

6 years, 10 months

1
1
0 0

[xwiki-devs] [Need proposal] How to show "conflicting" macro parameters

by Thomas Mortagne

Hi xwikiers, In the contact of bringing new Page concept (OK 7.4 is starting to get old) to the API and macros too we decided (1) to introduce a "page" shortcut property (even if we keep the reference/type for other types). While it's nicer for wiki syntax, one issue is that on WYSIWYG macros UI side, which display all properties, it means ending up with conflicting parameters that needs to be displayed as such. I don't really have much clue on how best to display this so I'm searching for ideas :) Then I will add in the macro descriptor what's required for whatever UI we want to build (group and sub groups of properties, etc.). 1: http://design.xwiki.org/xwiki/bin/view/Proposal/DeprecatingSpaceAndSpaceRef… Thanks, -- Thomas Mortagnes

6 years, 10 months

4
37
0 0

[xwiki-devs] [Proposal] Update servlet container support strategy

by Vincent Massol

Hi devs, We now have https://dev.xwiki.org/xwiki/bin/view/Community/ServletContainerSupportStrat… but it’s not precise enough. I’m proposing the following: * Mention the supported version cycle and mention that we support the latest version of the cycle. * For Tomcat, I propose to say we support Tomcat 8.x (which means Tomcat 8.5.34 as of today, see “latest” tag on https://hub.docker.com/_/tomcat/) * For Jetty (standalone packaging or standard), I propose to say we support Jetty 9.x (which means Jetty 9.4.12 as of today, see “latest” tag on https://hub.docker.com/_/jetty/) WDYT? Thanks -Vincent

6 years, 10 months

5
14
0 0

[xwiki-devs] [UX] Simpler Upgrades

by Ecaterina Moraru (Valica)

Hi devs, I've heard that the upgrade process is a complicated process and relies on a lot of manual operations. I haven't investigated the technical solutions we have at our disposal, but I tried to image the desired UI an Administrator would want when upgrading: * be notified that a new version is available: https://design.xwiki.org/xwiki/bin/download/Proposal/Upgrade/SimplerUpgrade… * have an upgrade section in Administration where Distribution and Extensions can be checked for new versions and upgraded / backed: https://design.xwiki.org/xwiki/bin/download/Proposal/Upgrade/SimplerUpgrade… https://design.xwiki.org/xwiki/bin/download/Proposal/Upgrade/SimplerUpgrade… A more detailed proposal at https://design.xwiki.org/xwiki/bin/view/Proposal/Upgrade/SimplerUpgrade/ So, what are your thoughts on this? Thanks, Caty

6 years, 10 months

3
6
0 0

[xwiki-devs] [Brainstorming] Should we merge the 3 xwiki repos: commons, rendering & platform?

by Vincent Massol

Hi devs, I’d like to start/revisit a brainstorming on the idea of merging the 3 xwiki repos: commons, rendering & platform. Pros: * Nicer to have XWiki Standard be contained in a single repo * More logical since we release the 3 at the same time with the same versions * Simpler to commit. Right now if you make changes that affect more than 1 repo we get failures in the CI + we need several jira issues ideally + developers need to rebuild locally the changes from the other repo or wait for the CI to finish building the changes (takes long). * Simpler for users to report issues. One jira project is simpler to know where to report. * Less CI jobs * Simpler for running tools like jacoco, clover, etc since they can run in a singe maven reactor. * Simpler for releases (e.g. to find the list of committers for the RN, you need to run the command only once instead of 3 times, etc) * Simpler to understand the xwiki code base and for onboarding Cons: * We need to find a solution for Maven plugins that need to be build before they’re used (XAR plugin, Package plugin, etc). One solution for those is to have them in a separate repo and using the last released version for their XWiki dependencies. Unless it now works with Maven to build plugins in the same reactor as where they’re used (need to try it). * Maybe could cause memory issues when running the whole build in a single maven reactor? * Note that I don’t think this would impact the release of commons and rendering modules to Maven Central since we can still configure that in the poms for those modules. * We might need to refactor some of our build checking tools such as the one verifying that commons doesn’t use rendering or platform modules but that’s not a big deal. * Possibly slightly longer paths for building on windows (see below) If we were to agree on the merge, we could keep the separation between the 3 repos with directories and have an addition level such as: xwiki (repo) |_ xwiki-commons |_ xwiki-rendering |_ xwiki-platform Now we could also forge this organization and flatten it with: xwiki (repo) |_ xwiki-(feature) |_ xwiki-(feature)-(subname1) For example: xwiki |_ xwiki-core |_ xwiki-component |_ xwiki-component-api (from commons) |_ xwiki-component-multi (from platform) |_ xwiki-rendering |_ … |_ xwiki-tools We could even try to go with an even flatter structure: xwiki |_ xwiki-component |_ xwiki-component-api (from commons) |_ xwiki-component-multi (from platform) |_ xwiki-rendering |_ … |_ xwiki-tools |_ ... (it would mean that in xwiki-tools, we apply similar rules that for runtime code or override the maven configs) WDYT? Thanks -Vincent

6 years, 10 months

5
10
0 0

[xwiki-devs] [XWiki Day] BFD#196

by Oana-Lavinia Florean

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

6 years, 10 months

1
1
0 0

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

by Vincent Massol

Hi devs, Here’s a proposal for 10.10 (discussed already with the persons mentioned below). Date: November 2018 Scope: BAU: * Thomas/Vincent: Improve STAMP KPIs (20%) * All: BFD (20%) Outstanding work: * Thomas: continue work on performance (started in 10.4). Goal: go back to XWiki 8.x performance! * Specifically commit the work already done on the asynchronous framework/macro + apply it for UIX + panels + other places - Status: work already done mostly, will require a few more days * Other performance-related topics * Simon/Marius (moved from 10.8 roadmap): Macro inline editing in WYSIWYG * Work mostly done but there are still some leftovers, especially in https://jira.xwiki.org/browse/XRENDERING-518 which is proving harder than expected. Since it’s already late in the release, it’ll be committed in 10.10RC1. * Adel (moved from 10.8 roadmap): finish applying Autocomplete on reference everywhere, * We have one issue that is in 10.9. The rest is ready but will be committed in 10.10 only (too late for 10.9). * Simon: Page Move/Renaming: don't allow and/or warn when moving pages containing xclass definitions. Use case: prevent users from breaking AWM apps they created * Work finished but too late to be in 10.9. Will now be in 10.10 * Adel/Marius (moved from 10.8 roadmap): Auto complete of references in WYSIWYG Macro Dialog (+ grouping feature so that users don't get both "page" and "reference" at the same time + "deprecated"/"priority" to show "page" more proemintenly than "reference") * Guillaume: fix outstanding issues for notifications New work: * Simon: Button to remove all deleted pages/attachments in a single click Best effort (if time permits, the items below are previous leftovers from previous roadmaps or items originally planned for 10.10): * Marius/Adel/Simon: ConfigurableClass doesn't support page level configuration ccse * Marius/Adel/Simon: Import: make it work with new versions of Libre Office (idea: use a more recent fork of jodconverter, we identified one and check if we need to merge changes we did in our fork) * Marius/Adel/Simon: Display Reference of documents to copy paste * Marius/Adel/Simon: Improve the XClass picker when in object edit mode (make it like the Add Macro dialog for WYSIWYG editor) * Thomas: work on some items to make the upgrade experience simpler + unattended upgrades (ability to upgrade XWiki from the command line without interaction). Use the result of Caty's investigation from XWiki 10.8 period. Dates: * 10.10RC1: 19th of November 2018 * 10.10Final: 26th of November 2018 I’ve also updated https://www.xwiki.org/xwiki/bin/view/Roadmaps/ If you’re ok with the proposal please edit https://www.xwiki.org/xwiki/bin/view/Roadmaps/ and add the individual jira issues that you’re taking for 10.10 for the mentioned topics. Thanks! -Vincent

6 years, 10 months

1
0
0 0

[xwiki-devs] [XWiki Day] BFD#194

by Oana-Lavinia Florean

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

6 years, 10 months

1
1
0 0

[xwiki-devs] [Proposal] Delete all in the recycle bin

by Simon Urli

Hi everyone, I'll work this month on adding the "delete all" functionality in the recycle bin. However I'd like to have your opinion on how it should looks like for the users. I have at least 4 proposals that I detailed there: https://design.xwiki.org/xwiki/bin/view/Proposal/Deleteallfromrecyclebin The 4 proposal are numbered as following: A. A simple button B. A simple button with a checkbox to activate it C. A button and a modal to confirm the action D. A generic bulk action on the livetable Thanks in advance for your feedbacks. Simon -- Simon Urli Software Engineer at XWiki SAS simon.urli(a)xwiki.com More about us at http://www.xwiki.com

6 years, 10 months

6
22
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs