Archive

With the release of 9.5.1 we have dropped the XWiki Enterprise distribution and instead we exposed the Flavor mechanism. Now when you install or create a new wiki you will be able to choose the Flavor you want to use. We expect in the future that the community members will provide additional Flavors built on top of XWiki and you could select between them when customizing your wiki. ...

The XWiki development team is proud to announce the availability of XWiki 9.5.1. This version fix important bugs found in 9.5: broken flavor picker in the Distribution Wizard, broken sub wiki template creation and missing extensions notifications in the profile. ...

This release brings lots of usability improvements: improved Livetable filtering (Date filters, Multilist filters, DBList filters), Page Templates can now be auto-selected based on the current location, simplified way of adding a logo to a Color Theme and a lot more. In addition, the new Notifications feature has been worked on too: grouping of related notifications, ability to send emails, configuration of locations and sending diffs in emails. Last but not least: XWiki Enterprise is dead! We now have a new XWiki distribution that asks you at startup what Flavor you'd like to use for your wiki, and we're providing a default Flavor called the Standard Flavor (the closest to the previous XWiki Enterprise distribution). In the future there should be more Flavors offered. ...

This release features a major restructuring of the XWiki Enterprise distribution by converting it into the XWiki Standard Flavor. User features cover notifications by email, attachments list showing icons and image previews, recommended template at page creation, LiveTable date and multilist filters, and minor visual improvements. Admins can more easily customize the look and feel by the extended use of Icon Themes and the improvements done to setting the wiki logo. Finally, devs have a new API for working with wiki components, new icon theme mappings and notifications API improvements. ...

This Thursday we had our Bug Fixing Day #144. We've managed to close 6 bugs (4 real fixes) with 2 participants. We are still at -66 bugs behind the 500 days period. ...

When we run our functional tests (we use Selenium2/Webdriver), we record a screenshot when a test fails. Previously we had a Groovy Scriptler script (written by Eduard Moraru, an XWiki committer) to automatically change the description of a Jenkins test page to include the screenshot. This blog post explains the solution found to port it to a Jenkins Pipeline script. ...

On June 1st we had our seventh Test Day. Vincent worked on our Jenkins build to convert old style jobs into new fancy pipelines. ...