+1 Le 17 nov. 2010 à 11:50, Vincent Massol a écrit :

Hi devs,

We've already branched XE .6 and thus trunk is already 2.7 so we're late on the 2.7 roadmap. Let's define it quickly.

Following our past discussions I'm proposing that XE 2.7 be also a short "stabilization" release in the same manner that 2.6 was a stabilization release (but without new major features - we've introduced revamped dashboard + mail to page in 2.6).

The idea is to finish what we have started: - fix bugs - fix UI inconsistencies - fix usability issues (especially for the recently introduced features such as the new activity stream and mail to page) - fix browser compatibility issues - make sure our APIs are as stable as possible and we don't leave APIs that we don't want to continue to support in the 3.x cycle

Proposed dates:

- XE 2.7M1: 6 Dec 2010 (2 weeks and 1 day from the XE 2.6 final release - 3 weeks from the XE 2.6 branch creation) - XE 2.7RC1: 13 Dec 2010 (1 week after M1) - XE 2.7 final: 20 Dec 2010

This would give a XE 2.7 release for Christmas (and the end of the 2.x cycle, except for bugfix releases) ! ;)

WDYT?

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

+1 Thanks, Marius On 11/17/2010 12:50 PM, Vincent Massol wrote:

Hi devs,

We've already branched XE .6 and thus trunk is already 2.7 so we're late on the 2.7 roadmap. Let's define it quickly.

Following our past discussions I'm proposing that XE 2.7 be also a short "stabilization" release in the same manner that 2.6 was a stabilization release (but without new major features - we've introduced revamped dashboard + mail to page in 2.6).

The idea is to finish what we have started: - fix bugs - fix UI inconsistencies - fix usability issues (especially for the recently introduced features such as the new activity stream and mail to page) - fix browser compatibility issues - make sure our APIs are as stable as possible and we don't leave APIs that we don't want to continue to support in the 3.x cycle

Proposed dates:

- XE 2.7M1: 6 Dec 2010 (2 weeks and 1 day from the XE 2.6 final release - 3 weeks from the XE 2.6 branch creation) - XE 2.7RC1: 13 Dec 2010 (1 week after M1) - XE 2.7 final: 20 Dec 2010

This would give a XE 2.7 release for Christmas (and the end of the 2.x cycle, except for bugfix releases) ! ;)

WDYT?

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

On 11/17/2010 05:50 AM, Vincent Massol wrote:

Hi devs,

We've already branched XE .6 and thus trunk is already 2.7 so we're late on the 2.7 roadmap. Let's define it quickly.

Following our past discussions I'm proposing that XE 2.7 be also a short "stabilization" release in the same manner that 2.6 was a stabilization release (but without new major features - we've introduced revamped dashboard + mail to page in 2.6).

The idea is to finish what we have started: - fix bugs - fix UI inconsistencies - fix usability issues (especially for the recently introduced features such as the new activity stream and mail to page) - fix browser compatibility issues

- make sure our APIs are as stable as possible and we don't leave APIs that we don't want to continue to support in the 3.x cycle This is a big job and I will be happy to do what I can for it. Should we break the apis for 2.7 or just deprecate them and then only break for 3.0?

+1 overall Caleb

Proposed dates:

- XE 2.7M1: 6 Dec 2010 (2 weeks and 1 day from the XE 2.6 final release - 3 weeks from the XE 2.6 branch creation) - XE 2.7RC1: 13 Dec 2010 (1 week after M1) - XE 2.7 final: 20 Dec 2010

This would give a XE 2.7 release for Christmas (and the end of the 2.x cycle, except for bugfix releases) ! ;)

WDYT?

Thanks -Vincent

_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs

Uploaded on http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap#HXWikiEnterprise2.7 Feedback received: 5 +1 (bindings), 2 +1 (non binding) and one 0. Let's do it! Thanks -Vincent On Nov 17, 2010, at 11:50 AM, Vincent Massol wrote:

Hi devs,

We've already branched XE .6 and thus trunk is already 2.7 so we're late on the 2.7 roadmap. Let's define it quickly.

Following our past discussions I'm proposing that XE 2.7 be also a short "stabilization" release in the same manner that 2.6 was a stabilization release (but without new major features - we've introduced revamped dashboard + mail to page in 2.6).

The idea is to finish what we have started: - fix bugs - fix UI inconsistencies - fix usability issues (especially for the recently introduced features such as the new activity stream and mail to page) - fix browser compatibility issues - make sure our APIs are as stable as possible and we don't leave APIs that we don't want to continue to support in the 3.x cycle

Proposed dates:

- XE 2.7M1: 6 Dec 2010 (2 weeks and 1 day from the XE 2.6 final release - 3 weeks from the XE 2.6 branch creation) - XE 2.7RC1: 13 Dec 2010 (1 week after M1) - XE 2.7 final: 20 Dec 2010

This would give a XE 2.7 release for Christmas (and the end of the 2.x cycle, except for bugfix releases) ! ;)

WDYT?

Thanks -Vincent