The XWiki development team is proud to announce the availability of XWiki
7.0 Milestone 1.
This is the first milestone release of the 7.x cycle. It features a
Document Index Tree Finder for the Index Application, integration of the
new Tree Widget with the WYSIWYG editor and some usability improvements.
Developers have a new Finder Plugin for the Tree Widget and the old Lucene
search module was finally retired to Contrib.
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/ReleaseNotesXWiki70M1
Thanks
-The XWiki dev team
Hi devs,
This is exciting times as we’re starting a new cycle for XWiki: XWiki 7.x! :)
Here are some proposals below that I have discussed with committers from XWiki SAS already.
For all other committers (thinking about Denis, Sergiu, Clemens, Andreas or other), feel free to add other stuff you’d like to do in 7.0.
Cycle Dates
============
I’d like to propose the following cycle dates:
- 7.0: March (Feb-Mar )
- 7.1: May (Apr-May )
- 7.2: July (Jun-Jul)
- 7.3: September (Aug-Sep)
- 7.4: November (Oct-Nov )
This leaves us one month for adjustment, for the almost impossible possibility that we’d be late in one of these major releases :)
XWiki 7.0 Dates
===============
- 7.0M1: 9 Feb
- 7.0M2: 2 march
- 7.0RC1: 16 march
- 7.0Final: 30 march
Wiki 7.0 Content
================
- Improve upgrade tools - Improve DW - Dev: Marius
- Continue performance improvements - Dev: Thomas
- Flavor mechanism - Dev: Thomas
- Notifications improvements (e.g. Immediate mail notif in watchlist + immediate notif in comment) - Dev: Edy
- Full integration of new technologies (less, bootstrap) in XWiki so that they can be fully used for client projects - it can also be only documentation - Dev: Guillaume
- Implement the “XWiki Core” strategy as defined in http://markmail.org/message/keo7cs6u3fuf676w - Dev: Vincent
Some important JIRAs (several of them should be taken up when defining what to implement from the general list above):
- Extension Manager add extension search should suggest only compatible versions - XWIKI-9920
- Sometimes rights changes don't apply without a server restart (confidential, FOR 6.4.x) - XWIKI-11355
- Add a simulation feature to the distribution wizard - XWIKI-11502
- Notify Wiki owners by email when users [request to] join their wiki - XWIKI-11096
- Support LESS in SSX objects - XWIKI-11394
- Presentation Office documents (.ppt files) aren't displayed with LibreOffice 4.3.5.2 - XWIKI-11611
- Know who has installed an extension and when - XWIKI-10027
- Add a reload button for changing the CAPTCHA message at registration - XWIKI-9879
- Do not display a very long title in the wiki's header - XWIKI-11234
- Remove the need for the "Finalize" button at the end of the process of wiki creation from template (FOR 6.4.x?) - XWIKI-11527
- Renaming a page changes the creation date - XWIKI-9425
- Exporting/Replaying the upgrade log - XWIKI-11504 XWIKI-11505 XWIKI-11074
Investigations:
- Better WYSIWYG editor - CKEditor investigation (1 Week) - Marius
- Better captcha module - Edy
Let me know if there are any concerns.
Thanks a lot
-Vincent
Hi devs,
I don’t recall if we had already agreed to this proposal or not so now that I’ve progressed with its implementation I’m sending this mail to ensure we all agree.
Rationale:
* The build logs should not be polluted with “normal” stack traces, or any message. Anything that the test produces should be contained and asserted in the test itself.
* If some logs go through it means they’ve not been captured and not been asserted in the test.
* It makes the test writer more aware of what the code being tested outputs and thus what the test writer needs to do about these.
Implementation details:
* Fail the build if some unit test output content to stdout or stderr.
* By default any code that outputs log will send content to stdout (since by default slf4j/logback will use a Console Appender that logs to stdout).
* Thus when code output logs, the test need to capture those logs. I’m introduced a new rule (@AllLogRule - see https://gist.github.com/vmassol/d6357901fca25db74783) which captures all logs.
* The @AllLogRule rule will fail the test if the captured logs are not asserted (it can be asserted for its content or the test can explicitly say it doesn’t care about it).
* There will be a custom RunListener (CaptureConsoleRunListener - see https://gist.github.com/vmassol/f3b7496b5bd3a9693fc2) plugged into the Maven Surefire plugin that fails the build if there’s content sent to stdut/stderr
* Our Maven build will perform the check by default and we’ll start by disabling it in the modules that currently fail.
* The idea is that slowly over time we remove the disabling in those modules as we fix the tests and that for new modules we apply the new rule (which will be enabled by default)
Example of capturing/asserting logs:
@Rule
public AllLogRule logRule = new AllLogRule();
…
assertEquals("Error getting resource [bad resource] because of invalid path format. Reason: [invalid url]",
this.logRule.getMessage(0));
Example of ignoring a log:
…
assertNotNull(this.logRule.getMessage(0));
WDTY?
Thanks
-Vincent
Hi devs,
In order to implement http://markmail.org/message/hfbzej4rh6ufqaud I need to find a place for the custom RunListener.
I’m proposing to define xwiki-commons-tools (and xwiki-platform-tools) as the place for:
- modules that are used at build time (ie that server to build the other modules)
- modules that are not required at runtime
As such it’s logical to move the commons-test & platform-test modules as tools modules.
Specifically:
* Move xwiki-commons/xwiki-commons-test/ to xwiki-commons/xwiki-commons-tools/xwiki-commons-tool-test/
* Move xwiki-platform/xwiki-platform-test/ to xwiki-platform/xwiki-platform-tools/xwiki-platform-tool-test/
WDYT?
Thanks
-Vincent
Hello.
I just have created a new project:
https://github.com/xwiki-contrib/application-wikiflavor
This project gives to the user to possibility to chose a flavor when she
creates a new wiki. It is designed to run on a 6.4.x instance, and some of
this work will probably be integrated in xwiki-platform during the 7.x
cycle (probably not in 6.4.x which is supposed to be a stabliization
release).
Among other things, it creates and provisions new wikis in a single job, so
there is no need to click on the "finalize" button at the end of the wiki
creation, and Distribution Wizard is not displayed anymore when you access
to the created wiki for the first time.
The application is described on its extension page:
http://extensions.xwiki.org/xwiki/bin/view/Extension/Wiki+Flavor+Application
It actually fixes some issues:
- http://jira.xwiki.org/browse/XWIKI-11527 - Remove the need for the
"Finalize" button at the end of the process of wiki creation from template
- http://jira.xwiki.org/browse/XWIKI-10043 - Put the wiki creation inside a
job
- http://jira.xwiki.org/browse/XWIKI-10566 - Include Distribution Wizard
and the wiki creation in a single job and display DW only if the users do
not want the default UI (partially)
Thanks,
--
Guillaume Delhumeau (gdelhumeau(a)xwiki.com)
Research & Development Engineer at XWiki SAS
Committer on the XWiki.org project