Hi devs,
Here’s a proposal for the 5.4 and 5.5 *stabilization* releases.
General goals: Finish all big domains started in the 5.x cycle.
Content
======
* Continue fixing and stabilizing:
** EM/DW - Thomas/Marius
** SOLR Search - Marius
** Multiwiki - GuillaumeD
** Scalable import/export + Confluence import - Thomas
* Script signing - Denis
* Continue BFD but with a priority of fixing issues for the 5.x cycle (i.e. issues from
the listed domains above). Also since we’re stabilizing, nothing dangerous should be
committed and if a dev is not 100% sure about the consequences of what he’s doing he
should raise it and ask for reviews (possibly go through pull requests).
Here’s an ordered of important JIRA issue (top priority first). The goal is to try to do
the maximum but it’s a best effort and some issues are too dangerous/complex for the 5.x
cycle:
- When upgrading a wiki, do not display what happened (files edited, etc.) in the Activity
Stream - XWIKI-8765
- Scheduler / Watchlist activity shouldn't add a version to the page. Huge xwikircs
table and terrible performances when reading it.
- Creating an object changes the content author - XWIKI-9292
- Support 2 roles for users for app within minutes: application creator and data creator
- XWIKI-8757
- Make several separate blogs in one xwiki - XWIKI-6348
- Wysiwyg no image resizing on Chrome
- xwiki.cfg & xwiki.properties merging
- Add default column and sort choices in AppWithinMinutes livetable setting XWIKI-9659
- Save & view a section should go to the section anchor instead of the top of the
document XE-1335
- Activity Stream should not show deleted documents that was hidden. - XWIKI-9544
- Add a message for the Livetable's empty state - XWIKI-7821
- "Space Templates" should also create the space preferences page - XWIKI-9712
- The Wiki UIExtensions should check the rights before executing extension points
- XWIKI-9156
Please add more if you’re planning to work on something not listed.
Investigations:
- Investigation bugs specific IE10/IE11 - Sorin/Manuel. Depending on the result we may
want to add support for IE10 in 5.5.x.
Dates
=====
One goal is to try to keep 5.x cycle as close to 2013 as possible so that we can align
cycles on calendar years and have a 6.x final at the end of 2014...
Proposal 1:
=========
- 5.4M1: 30th of Dec
- 5.4RC1: 13th of Jan 2014
- 5.4 Final: 20th of Jan 2014
- 5.5M1: 27th of Jan 2014
- 5.5RC1: 10th of Feb 2014
- 5.5 Final: 17th of Feb 2014
Proposal 2:
=========
Group together 5.4 and 5.5 and increase timeframe of 5.4 and have bugfix release of 5.5 if
needed.
- 5.4M1: 6th of Jan 2014
- 5.4RC1: 20th of Jan 2014
- 5.4Final: 27th of Jan 2014
This solution allows us to end the 5.x cycle in Jan 2014 as planned and start 6.x at
beginning of Feb 2014. And important issues get fixed as bug fix releases of 5.4.x (5.4.1,
5.4.2, etc).
WDYT?
Thanks
-Vincent