This is the release notes for XWiki Commons, XWiki Rendering, XWiki Platform and XWiki Enterprise. They share the same release notes as they are released together and have the same version.

This version does not contains many changes as most committers were working on contrib extensions. It still introduced a new administration UI to help manage available syntaxes.

New and Noteworthy (since XWiki 8.2 Milestone 1)

Full list of issues fixed and Dashboard for 8.2.

Configure Syntaxes in Administration UI

It's now possible to easily configure the markup syntaxes that you wish to be made available to your users when writing pages, directly from the Admin UI.

We've also modified the default syntax configuration when you start with a fresh new XWiki; by default the only configured syntax is the XWiki Syntax 2.1. To add more you need to install extensions offering new syntaxes or go to the Admin UI to configure more syntaxes for those bundled by default in XWiki.

Note that the xwiki/2.1 syntax is the only configured syntax by default now (we used to also have the xwiki/2.0 syntax too but we want to incitate users to use the newest syntax). In addition when the user is an Admin and only 1 syntax is configured, a hint is given to the user to let him know he can configure more syntaxes:

Miscellaneous

• Default XWiki Syntax 1.0 configuration has been removed from xwiki.cfg and is now documented here.
• You now have the option to create a blog post from anywhere inside the Blog page (or one of its children) by simply using the + (create page) button and selecting Blog Post as your new page's type:

  

See the full list of JIRA issues fixed in this release.

For Developers

Upgrades

The following dependencies have been upgraded:

• cssparser 0.9.19
• Tika 1.13
• HSQLDB 2.3.4
• Infinispan 8.2.2
• Pygments 2.1.3
• Commons FileUpload 1.3.2
• Joda-Time 2.9.4
• httpasyncclient 4.1.1
• old Jackson 1.9.13
• JBoss Logging 3.3.0
• javax.mail 1.4.7

Miscellaneous

• The URL API module (xwiki-platform-url-api) now provides an EntityReferenceResolver<String> resolver and an EntityReferenceSerializer<String> serializer implementations (with hint url) that can be used to parse/serialize EntityReference when used in URLs. The rationale is that Tomcat, for security reasons, doesn't support forward and backward slashes (/, \) in URLs by default. Thus, if a reference contains some reserved characters such as dot (.), colon (:), etc and you use a default serializer they'll be escaped using a backslash, leading to problems under Tomcat. So this resolver/serializer uses a different escape character (namely, it uses !)

Translations

The following translations have been updated: 

• Catalan
• German
• Spanish
• French
• Latvian
• Dutch
• Portuguese (Brazil)
• Russian
• Slovak

Tested Browsers & Databases

Here is the list of browsers we support and how they have been tested for this release:

	Browser	Test Result
	Google Chrome	Not Tested
	Mozilla Firefox	Not Tested
	Internet Explorer 10	Not Tested
	Internet Explorer 11	Jira Tickets Marked as Fixed in the Release Notes

Here is the list of databases we support and how they have been tested for this release:

	Database	Test Result
	HyperSQL	Not Tested
	MySQL 5.7.11	Jira Tickets Marked as Fixed in the Release Notes
	Oracle	Not Tested
	PostgreSQL	Not Tested

Known issues

• Bugs we know about

Backward Compatibility and Migration Notes

General Notes

When upgrading make sure you compare your xwiki.cfg, xwiki.properties and web.xml files with the newest version since some configuration parameters may have been modified or added. Note that you should add xwiki.store.migration=1 so that XWiki will attempt to automatically migrate your current database to the new schema. Make sure you backup your Database before doing anything.

Issues specific to XWiki XWiki 8.2 Milestone 1

• The xwiki.rendering.syntaxes configuration property from xwiki.cfg has changed purpose. It's now used only to define the initial list of active syntaxes. Then an Admin can go to the Admin UI to enable or disable syntaxes.
• Support for the Markdown syntax is no longer bundled by default and needs to be installed as an Extension if needed.

API Breakages

There was no API breakage in 8.2 Milestone 1.