20 Mar
2009
20 Mar
'09
6:33 p.m.
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
Note: I don't think we can commit to have a new skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
Thanks
-Vincent
20 Mar
20 Mar
6:48 p.m.
Vincent Massol wrote:
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
I think it is important to finally do some profiling and improve the
bottlenecks. One thing that's been causing a lot of problems is the
attachments storage that's a memory hog. Another is excessive cloning of
XWikiDocument objects, which should be improved by both improving the
clone performance and reducing the number of clones created.
Note: I don't think we can commit to have a new
skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
As always, I'd like a bit more time between 1.8 and 1.9M1, but I'll go
with the majority.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
7:56 p.m.
On Mar 20, 2009, at 6:48 PM, Sergiu Dumitriu wrote:
Vincent Massol wrote:
You can consider 1.9M1 has been started for 2 weeks already since 1.8
final was planned 2 weeks ago initially... :) My initial roadmap for
1.9 final was 2 weeks earlier but I've delayed it by 2 weeks to
account for the slippage in XE 1.8.
Thanks
-Vincent
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another
stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is
released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0
-->
2.0 syntax converter) for 1 year. This is the time we have to make
our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) -
All
* Refactoring of apps to use more of SSX - Jerome?
I think it is important to finally do some profiling and improve the
bottlenecks. One thing that's been causing a lot of problems is the
attachments storage that's a memory hog. Another is excessive
cloning of
XWikiDocument objects, which should be improved by both improving the
clone performance and reducing the number of clones created.
Note: I don't think we can commit to have a
new skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
As always, I'd like a bit more time between 1.8 and 1.9M1, but I'll go
with the majority. 
8:16 p.m.
On Fri, Mar 20, 2009 at 10:48 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
I think it is important to finally do some profiling
and improve the
bottlenecks. One thing that's been causing a lot of problems is the
attachments storage that's a memory hog. Another is excessive cloning of
XWikiDocument objects, which should be improved by both improving the
clone performance and reducing the number of clones created.
What about just using the filesystem to store attachment files 'as-is'. Use
the database to hold the filename and it's relation to the unique identifier
that is the filename. Use separate directories representing wikis, and
subdirectries representing spaces. I.e. each space has it's own directory of
attachments all filenames per directory unique. This implementation
will not do attachment versioning or attachment recycle-bin which will be
forced ''off'. If you delete an attachment, you'll just have to go back
to
where you got it from originally and get another....
In other words, I think there should be a xwiki.cfg switch which says
whether to use external attachments or not, and migration tools that migrate
attachments from the database to the filesystem for systems where this new
feature gets "turned on." Leave it off and continue to get the old behavior
with database-based attachments.
Alternately, at least, turn off attachment versioning and recycle-bin by
default. Preventing problems like this
http://n2.nabble.com/Hibernate-exception-when-trying-to-delete-attachment-t…
-- Niels
http://nielsmayer.com
6:55 p.m.
Vincent Massol wrote:
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
I sure can help with this, but I'm not sure of what value it brings for
1.9. Potentially it can introduce some bugs, so I would rather do this
after XE 2.0 (same for a general refactoring of xwiki's javascript)
In the mean time, if we still agree we want it for 1.9, I am still
committed to write support for velocity/script wiki macro bridge.
+1 for the general objectives of 1.9 and for the dates.
Jerome
Note: I don't think we can commit to have a new skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
8:39 p.m.
On Mar 20, 2009, at 6:55 PM, Jerome Velociter wrote:
Vincent Massol wrote:
Yes you're right. This should not be a first level objective. We
should focus on bug fixes as much as possible.
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another
stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is
released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0
-->
2.0 syntax converter) for 1 year. This is the time we have to make
our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) -
All
* Refactoring of apps to use more of SSX - Jerome?
I sure can help with this, but I'm not sure of what value it brings
for
1.9. Potentially it can introduce some bugs, so I would rather do this
after XE 2.0 (same for a general refactoring of xwiki's javascript) In the mean time, if we still agree we want it for
1.9, I am still
committed to write support for velocity/script wiki macro bridge.
Yes definitely for that bridge.
Thanks
-Vincent
+1 for the general objectives of 1.9 and for the
dates.
Jerome
>
> Note: I don't think we can commit to have a new skin system or a new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
>
> WDYT?
>
> Thanks
> -Vincent
> _______________
23 Mar
23 Mar
12:29 a.m.
We could also add
- the RSS refactoring which was mostly done by Marius.
- include the Excel plugin in the standard distrib
- handling of velocity macros
- Macro libraries and improved macro inserting
Also concerning 1.8.1 there are a few features/bug fixes that we need to
include as Curriki is depending on it and it won't be possible to wait
for 1.9 for them.
- Insert Attachment
- Font/Size/Colors management
- Sufficient wysiwyg parameters to show/hide certains features in the
dialog boxes
Ludovic
Vincent Massol a écrit :
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
Note: I don't think we can commit to have a new skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
9:13 a.m.
On Mar 23, 2009, at 12:29 AM, Ludovic Dubost wrote:
We could also add
- the RSS refactoring which was mostly done by Marius.
- include the Excel plugin in the standard distrib
committers: Who would be able (read: have the time) to work on this?
- handling of velocity macros
This is already planned an included in "finish new rendering" and
assigned to Jerome.
- Macro libraries and improved macro inserting
I guess "improved macro inserting" is in the WYSIWYG editor. Could you
be more specific to see if it matches what Marius is working on?
Re "macro libraries" not sure what this is about. Is it about the
ability to load velocity macros in the Velocity Engine only once
(using for example the existing "velocity macros" field in the admin
(programming section)?
Thanks
-Vincent
Also concerning 1.8.1 there are a few features/bug
fixes that we
need to
include as Curriki is depending on it and it won't be possible to wait
for 1.9 for them.
- Insert Attachment
- Font/Size/Colors management
- Sufficient wysiwyg parameters to show/hide certains features in the
dialog boxes
Ludovic
Vincent Massol a écrit :
> Hi devs,
>
> XE 2.0
> =====
>
> We've had discussion about XE 2.0 in the past. I think now is the
> right time to release it and we should prepare to do so. Two reasons;
> 1) We've had a lot of new features (new rendering, new wysiwyg,
> webdav, REST, office import, usability improvements, etc) added
> recently in 1.8 and this alone warrants calling it 2.0. The new
> rendering and new wysiwyg could be set as default in XE 2.0.
> 2) XE 1.0 marked a stability level. XE 2.0 will mark another
> stability
> level (I'm thinking about the old wysiwyg editor which could be said
> to be stable...)
> 3) It's been almost exactly 2 years since we released XE 1.0, it's
> high time for a major release.
>
> However since we still have a bit of work to fully finish the new
> rendering and new wysiwyg and since we want user feedback from 1.8 to
> ensure we get a rock solid 2.0 release I propose to have a XE 1.9
> release before the XE 2.0 (which would be a promotion of XE 1.9 final
> with the config change to have new syntax/wysiwyg as defaults).
>
> The other advantage of releasing XE 2.0 is that we want to start the
> maintenance period for the old rendering/old wysiwyg as early as
> possible to get new people to use the new system. Once 2.0 is
> released
> we'll continue releasing bugfix versions of 1.9.x from time to time
> but we'll advise people to switch to 2.x. I propose we keep support
> for the old 1.0 syntax (either using the old code or using the 1.0
> -->
> 2.0 syntax converter) for 1 year. This is the time we have to make
> our
> existing users switch to the new syntax. Note that with the automatic
> converters it shouldn't be something too difficult.
>
> Roadmap for XE 1.9
> ================
>
> General:It's a stabilization release meaning we must resist putting
> new things in it and fix what doesn't work well enough.
>
> Content proposal:
> * Finish/stabilize/document new rendering - Thomas/Vincent
> * Finish/stabilize/document new wysiwyg editor - Marius/Anca
> * Finish/stabilize/document office importer + doc splitter/management
> - Asiri
> * Finish/stabilize/document webdav - Asiri
> * Finish/stabilize/document REST support - Fabio
> * Finish/stabilize/document new blog application - Sergiu/Guillaume
> * Continue UI improvements (ex: new treeview, new search interface,
> full list to be defined) - JV/Ecaterina/Guillaume
> * Fix search using lucene plugin - ????
> * Finish XE French translations - JV/Guillaume
> * Fix other bugs (watchlist, page names with special chars, etc) -
> All
> * Refactoring of apps to use more of SSX - Jerome?
>
> Note: I don't think we can commit to have a new skin system or a new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
>
> WDYT?
>
> Thanks
> -Vincent
9:39 a.m.
Vincent Massol a écrit :
For me it is to access the list of macros by a library first (with a
nice description)
Then it is listing the available macros with a nice description.
Then it is editing the parameters with a nice description for each
parameter and eventually some types params (lists, etc..) and controls
On Mar 23, 2009, at 12:29 AM, Ludovic Dubost wrote:
I can work on the Excel plugin. I just need to be told what to change.
We could also add
- the RSS refactoring which was mostly done by Marius.
- include the Excel plugin in the standard distrib
committers: Who would be able (read: have the time) to work on this?
- handling of velocity macros
This is already planned an included in "finish new rendering" and
assigned to Jerome.
- Macro libraries and improved macro inserting
I guess "improved macro inserting" is in the WYSIWYG editor. Could you
be more specific to see if it matches what Marius is working on?
Re "macro libraries" not sure what this is
about. Is it about the
ability to load velocity macros in the Velocity Engine only once
(using for example the existing "velocity macros" field in the admin
(programming section)?
Yes it is having a section on the admin that lists the available
libraries and have a easy way to add a new one (it can be standard XAR
import).
We should eventually be able to deactivate some libraries.
It should list libraries provided by the Wiki, by the XEM instance and
natively (macros.vm or rendering macros)
Ludovic
Thanks
-Vincent
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Also concerning 1.8.1 there are a few
features/bug fixes that we
need to
include as Curriki is depending on it and it won't be possible to wait
for 1.9 for them.
- Insert Attachment
- Font/Size/Colors management
- Sufficient wysiwyg parameters to show/hide certains features in the
dialog boxes
Ludovic
Vincent Massol a écrit :
> Hi devs,
>
> XE 2.0
> =====
>
> We've had discussion about XE 2.0 in the past. I think now is the
> right time to release it and we should prepare to do so. Two reasons;
> 1) We've had a lot of new features (new rendering, new wysiwyg,
> webdav, REST, office import, usability improvements, etc) added
> recently in 1.8 and this alone warrants calling it 2.0. The new
> rendering and new wysiwyg could be set as default in XE 2.0.
> 2) XE 1.0 marked a stability level. XE 2.0 will mark another
> stability
> level (I'm thinking about the old wysiwyg editor which could be said
> to be stable...)
> 3) It's been almost exactly 2 years since we released XE 1.0, it's
> high time for a major release.
>
> However since we still have a bit of work to fully finish the new
> rendering and new wysiwyg and since we want user feedback from 1.8 to
> ensure we get a rock solid 2.0 release I propose to have a XE 1.9
> release before the XE 2.0 (which would be a promotion of XE 1.9 final
> with the config change to have new syntax/wysiwyg as defaults).
>
> The other advantage of releasing XE 2.0 is that we want to start the
> maintenance period for the old rendering/old wysiwyg as early as
> possible to get new people to use the new system. Once 2.0 is
> released
> we'll continue releasing bugfix versions of 1.9.x from time to time
> but we'll advise people to switch to 2.x. I propose we keep support
> for the old 1.0 syntax (either using the old code or using the 1.0
> -->
> 2.0 syntax converter) for 1 year. This is the time we have to make
> our
> existing users switch to the new syntax. Note that with the automatic
> converters it shouldn't be something too difficult.
>
> Roadmap for XE 1.9
> ================
>
> General:It's a stabilization release meaning we must resist putting
> new things in it and fix what doesn't work well enough.
>
> Content proposal:
> * Finish/stabilize/document new rendering - Thomas/Vincent
> * Finish/stabilize/document new wysiwyg editor - Marius/Anca
> * Finish/stabilize/document office importer + doc splitter/management
> - Asiri
> * Finish/stabilize/document webdav - Asiri
> * Finish/stabilize/document REST support - Fabio
> * Finish/stabilize/document new blog application - Sergiu/Guillaume
> * Continue UI improvements (ex: new treeview, new search interface,
> full list to be defined) - JV/Ecaterina/Guillaume
> * Fix search using lucene plugin - ????
> * Finish XE French translations - JV/Guillaume
> * Fix other bugs (watchlist, page names with special chars, etc) -
> All
> * Refactoring of apps to use more of SSX - Jerome?
>
> Note: I don't think we can commit to have a new skin system or a new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
>
> WDYT?
>
> Thanks
> -Vincent
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
10:14 a.m.
Ludovic Dubost wrote:
Vincent Massol a écrit :
For me it is to access the list of macros by a library first (with a
nice description)
In JV's mockups macros are grouped by category. See
http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorInterface#HMacros
. I need a way to retrieve macros by category/library.
On Mar 23, 2009, at 12:29 AM, Ludovic Dubost
wrote:
I can work on the Excel plugin. I just need to be told what to change.
We could also add
- the RSS refactoring which was mostly done by Marius.
- include the Excel plugin in the standard distrib
committers: Who would be able (read: have the time) to work on this?
- handling of velocity macros
This is already planned an included in "finish new rendering" and
assigned to Jerome.
- Macro libraries and improved macro inserting
I guess "improved macro inserting" is in the WYSIWYG editor. Could
you
be more specific to see if it matches what Marius is working on?
Then it is listing the available macros with a nice
description.
I have the description. Now it is used as a tool tip for the macro title
in the Edit Macro dialog. I know, it's hidden.
Then it is editing the parameters with a nice
description for each
parameter and eventually some types params (lists, etc..) and controls
I have the parameter description and type. I don't have the list of
allowed values and the default value. The description is used as a tool
tip for the input control (again, it's hidden). The type is used to
choose the input control. Currently I have this mapping:
boolean/java.lang.Boolean -> BooleanInput (a combo box with three
options: yes, no, unspecified)
java.lang.String -> TextInput
What other controls would you like to have Ludovic?
Regarding the library/macro/parameter description we need to update the
UI design to take it into account. Maybe an information icon (like it
used to be in Curriki) near the library/macro/parameter would do. JV?
Thanks,
Marius
Re "macro libraries" not sure what this
is about. Is it about the
ability to load velocity macros in the Velocity Engine only once
(using for example the existing "velocity macros" field in the admin
(programming section)?
Yes it is having a section on the admin that lists the available
libraries and have a easy way to add a new one (it can be standard XAR
import).
We should eventually be able to deactivate some libraries.
It should list libraries provided by the Wiki, by the XEM instance and
natively (macros.vm or rendering macros)
Ludovic
Thanks
-Vincent
Also concerning 1.8.1 there are a few
features/bug fixes that we
need to
include as Curriki is depending on it and it won't be possible to wait
for 1.9 for them.
- Insert Attachment
- Font/Size/Colors management
- Sufficient wysiwyg parameters to show/hide certains features in the
dialog boxes
Ludovic
Vincent Massol a écrit :
> Hi devs,
>
> XE 2.0
> =====
>
> We've had discussion about XE 2.0 in the past. I think now is the
> right time to release it and we should prepare to do so. Two reasons;
> 1) We've had a lot of new features (new rendering, new wysiwyg,
> webdav, REST, office import, usability improvements, etc) added
> recently in 1.8 and this alone warrants calling it 2.0. The new
> rendering and new wysiwyg could be set as default in XE 2.0.
> 2) XE 1.0 marked a stability level. XE 2.0 will mark another
> stability
> level (I'm thinking about the old wysiwyg editor which could be said
> to be stable...)
> 3) It's been almost exactly 2 years since we released XE 1.0, it's
> high time for a major release.
>
> However since we still have a bit of work to fully finish the new
> rendering and new wysiwyg and since we want user feedback from 1.8 to
> ensure we get a rock solid 2.0 release I propose to have a XE 1.9
> release before the XE 2.0 (which would be a promotion of XE 1.9 final
> with the config change to have new syntax/wysiwyg as defaults).
>
> The other advantage of releasing XE 2.0 is that we want to start the
> maintenance period for the old rendering/old wysiwyg as early as
> possible to get new people to use the new system. Once 2.0 is
> released
> we'll continue releasing bugfix versions of 1.9.x from time to time
> but we'll advise people to switch to 2.x. I propose we keep support
> for the old 1.0 syntax (either using the old code or using the 1.0
> -->
> 2.0 syntax converter) for 1 year. This is the time we have to make
> our
> existing users switch to the new syntax. Note that with the automatic
> converters it shouldn't be something too difficult.
>
> Roadmap for XE 1.9
> ================
>
> General:It's a stabilization release meaning we must resist putting
> new things in it and fix what doesn't work well enough.
>
> Content proposal:
> * Finish/stabilize/document new rendering - Thomas/Vincent
> * Finish/stabilize/document new wysiwyg editor - Marius/Anca
> * Finish/stabilize/document office importer + doc splitter/management
> - Asiri
> * Finish/stabilize/document webdav - Asiri
> * Finish/stabilize/document REST support - Fabio
> * Finish/stabilize/document new blog application - Sergiu/Guillaume
> * Continue UI improvements (ex: new treeview, new search interface,
> full list to be defined) - JV/Ecaterina/Guillaume
> * Fix search using lucene plugin - ????
> * Finish XE French translations - JV/Guillaume
> * Fix other bugs (watchlist, page names with special chars, etc) -
> All
> * Refactoring of apps to use more of SSX - Jerome?
>
> Note: I don't think we can commit to have a new skin system or a new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
>
> WDYT?
>
> Thanks
> -Vincent
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:01 a.m.
On Mon, Mar 23, 2009 at 10:14, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
Ludovic Dubost wrote:
The default value is already easy to get from a macro parameter
instance but it need to be put into the MacroDescriptor.
Marius: is there jira for all informations to put in MacroDescription
you need for the WYSIWYG ? You can assign them all to me if it's a
priority for you I can take care of it.
Vincent Massol a écrit :
For me it is to access the list of macros by a library first (with a
nice description)
In JV's mockups macros are grouped by category. See
http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorInterface#HMacros
. I need a way to retrieve macros by category/library.
On Mar 23, 2009, at 12:29 AM, Ludovic Dubost
wrote:
I can work on the Excel plugin. I just need to be told what to change.
We could also add
- the RSS refactoring which was mostly done by Marius.
- include the Excel plugin in the standard distrib
committers: Who would be able (read: have the time) to work on this?
- handling of velocity macros
This is already planned an included in "finish new rendering" and
assigned to Jerome.
- Macro libraries and improved macro inserting
I guess "improved macro inserting" is in the WYSIWYG editor. Could you
be more specific to see if it matches what Marius is working on?
Then it is listing the available macros with a
nice description.
I have the description. Now it is used as a tool tip for the macro title
in the Edit Macro dialog. I know, it's hidden.
Then it is editing the parameters with a nice
description for each
parameter and eventually some types params (lists, etc..) and controls
I have the parameter description and type. I don't have the list of
allowed values and the default value. The description is used as a tool tip for the input control (again, it's hidden).
The type is used to
choose the input control. Currently I have this mapping:
boolean/java.lang.Boolean -> BooleanInput (a combo box with three
options: yes, no, unspecified)
java.lang.String -> TextInput
What other controls would you like to have Ludovic?
Current macros parameters also contains Enums. You should have a drop
down list for theses or something like this.
Regarding the library/macro/parameter description we need to update the
UI design to take it into account. Maybe an information icon (like it
used to be in Curriki) near the library/macro/parameter would do. JV?
Thanks,
Marius
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
Re "macro libraries" not sure what this
is about. Is it about the
ability to load velocity macros in the Velocity Engine only once
(using for example the existing "velocity macros" field in the admin
(programming section)?
Yes it is having a section on the admin that lists the available
libraries and have a easy way to add a new one (it can be standard XAR
import).
We should eventually be able to deactivate some libraries.
It should list libraries provided by the Wiki, by the XEM instance and
natively (macros.vm or rendering macros)
Ludovic
Thanks
-Vincent
Also concerning 1.8.1 there are a few
features/bug fixes that we
need to
include as Curriki is depending on it and it won't be possible to wait
for 1.9 for them.
- Insert Attachment
- Font/Size/Colors management
- Sufficient wysiwyg parameters to show/hide certains features in the
dialog boxes
Ludovic
Vincent Massol a écrit :
> Hi devs,
>
> XE 2.0
> =====
>
> We've had discussion about XE 2.0 in the past. I think now is the
> right time to release it and we should prepare to do so. Two reasons;
> 1) We've had a lot of new features (new rendering, new wysiwyg,
> webdav, REST, office import, usability improvements, etc) added
> recently in 1.8 and this alone warrants calling it 2.0. The new
> rendering and new wysiwyg could be set as default in XE 2.0.
> 2) XE 1.0 marked a stability level. XE 2.0 will mark another
> stability
> level (I'm thinking about the old wysiwyg editor which could be said
> to be stable...)
> 3) It's been almost exactly 2 years since we released XE 1.0, it's
> high time for a major release.
>
> However since we still have a bit of work to fully finish the new
> rendering and new wysiwyg and since we want user feedback from 1.8 to
> ensure we get a rock solid 2.0 release I propose to have a XE 1.9
> release before the XE 2.0 (which would be a promotion of XE 1.9 final
> with the config change to have new syntax/wysiwyg as defaults).
>
> The other advantage of releasing XE 2.0 is that we want to start the
> maintenance period for the old rendering/old wysiwyg as early as
> possible to get new people to use the new system. Once 2.0 is
> released
> we'll continue releasing bugfix versions of 1.9.x from time to time
> but we'll advise people to switch to 2.x. I propose we keep support
> for the old 1.0 syntax (either using the old code or using the 1.0
> -->
> 2.0 syntax converter) for 1 year. This is the time we have to make
> our
> existing users switch to the new syntax. Note that with the automatic
> converters it shouldn't be something too difficult.
>
> Roadmap for XE 1.9
> ================
>
> General:It's a stabilization release meaning we must resist putting
> new things in it and fix what doesn't work well enough.
>
> Content proposal:
> * Finish/stabilize/document new rendering - Thomas/Vincent
> * Finish/stabilize/document new wysiwyg editor - Marius/Anca
> * Finish/stabilize/document office importer + doc splitter/management
> - Asiri
> * Finish/stabilize/document webdav - Asiri
> * Finish/stabilize/document REST support - Fabio
> * Finish/stabilize/document new blog application - Sergiu/Guillaume
> * Continue UI improvements (ex: new treeview, new search interface,
> full list to be defined) - JV/Ecaterina/Guillaume
> * Fix search using lucene plugin - ????
> * Finish XE French translations - JV/Guillaume
> * Fix other bugs (watchlist, page names with special chars, etc) -
> All
> * Refactoring of apps to use more of SSX - Jerome?
>
> Note: I don't think we can commit to have a new skin system or a new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
>
> WDYT?
>
> Thanks
> -Vincent
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:05 a.m.
On Mar 23, 2009, at 10:14 AM, Marius Dumitru Florea wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Ludovic Dubost wrote:
Regarding categories I'm not sure this should go in the rendering
module. I don't think it's the role of each macro to say in which
category it is. It's more a user thing, i.e. it's the code using
macros that should probably decide of categories. I'm not fully sure
of this but I think categories depend really on the use case and
should not be fixed and thus should be decided/set by the user of
macros. The user could be the wysiwyg editor itself for now or it
could be some other UI module (not sure which).
Since I'm not sure I'd like to know what others think.
Thanks
-Vincent
Vincent Massol a écrit :
For me it is to access the list of macros by a library first (with a
nice description)
In JV's mockups macros are grouped by category. See
http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorInterface#HMacros
. I need a way to retrieve macros by category/library. On Mar 23, 2009, at 12:29 AM, Ludovic Dubost
wrote:
I can work on the Excel plugin. I just need to be told what to
change.
We could also add
- the RSS refactoring which was mostly done by Marius.
- include the Excel plugin in the standard distrib
committers: Who would be able (read: have the time) to work on this?
- handling of velocity macros
This is already planned an included in "finish new rendering" and
assigned to Jerome.
- Macro libraries and improved macro inserting
I guess "improved macro inserting" is in the WYSIWYG editor. Could
you
be more specific to see if it matches what Marius is working on?
Then it is
listing the available macros with a nice description.
I have the description. Now it is used as a tool tip for the macro
title
in the Edit Macro dialog. I know, it's hidden.
Then it is editing the parameters with a nice
description for each
parameter and eventually some types params (lists, etc..) and
controls
I have the parameter description and type. I don't have the list of
allowed values and the default value. The description is used as a
tool
tip for the input control (again, it's hidden). The type is used to
choose the input control. Currently I have this mapping:
boolean/java.lang.Boolean -> BooleanInput (a combo box with three
options: yes, no, unspecified)
java.lang.String -> TextInput
What other controls would you like to have Ludovic?
Regarding the library/macro/parameter description we need to update
the
UI design to take it into account. Maybe an information icon (like it
used to be in Curriki) near the library/macro/parameter would do. JV?
Thanks,
Marius
Re "macro libraries" not sure what this
is about. Is it about the
ability to load velocity macros in the Velocity Engine only once
(using for example the existing "velocity macros" field in the admin
(programming section)?
Yes it is having a section on the admin that lists the available
libraries and have a easy way to add a new one (it can be standard
XAR
import).
We should eventually be able to deactivate some libraries.
It should list libraries provided by the Wiki, by the XEM instance
and
natively (macros.vm or rendering macros)
Ludovic
Thanks
-Vincent
Also concerning 1.8.1 there are a few
features/bug fixes that we
need to
include as Curriki is depending on it and it won't be possible to
wait
for 1.9 for them.
- Insert Attachment
- Font/Size/Colors management
- Sufficient wysiwyg parameters to show/hide certains features in
the
dialog boxes
Ludovic
Vincent Massol a écrit :
> Hi devs,
>
> XE 2.0
> =====
>
> We've had discussion about XE 2.0 in the past. I think now is the
> right time to release it and we should prepare to do so. Two
> reasons;
> 1) We've had a lot of new features (new rendering, new wysiwyg,
> webdav, REST, office import, usability improvements, etc) added
> recently in 1.8 and this alone warrants calling it 2.0. The new
> rendering and new wysiwyg could be set as default in XE 2.0.
> 2) XE 1.0 marked a stability level. XE 2.0 will mark another
> stability
> level (I'm thinking about the old wysiwyg editor which could be
> said
> to be stable...)
> 3) It's been almost exactly 2 years since we released XE 1.0, it's
> high time for a major release.
>
> However since we still have a bit of work to fully finish the new
> rendering and new wysiwyg and since we want user feedback from
> 1.8 to
> ensure we get a rock solid 2.0 release I propose to have a XE 1.9
> release before the XE 2.0 (which would be a promotion of XE 1.9
> final
> with the config change to have new syntax/wysiwyg as defaults).
>
> The other advantage of releasing XE 2.0 is that we want to start
> the
> maintenance period for the old rendering/old wysiwyg as early as
> possible to get new people to use the new system. Once 2.0 is
> released
> we'll continue releasing bugfix versions of 1.9.x from time to
> time
> but we'll advise people to switch to 2.x. I propose we keep
> support
> for the old 1.0 syntax (either using the old code or using the 1.0
> -->
> 2.0 syntax converter) for 1 year. This is the time we have to make
> our
> existing users switch to the new syntax. Note that with the
> automatic
> converters it shouldn't be something too difficult.
>
> Roadmap for XE 1.9
> ================
>
> General:It's a stabilization release meaning we must resist
> putting
> new things in it and fix what doesn't work well enough.
>
> Content proposal:
> * Finish/stabilize/document new rendering - Thomas/Vincent
> * Finish/stabilize/document new wysiwyg editor - Marius/Anca
> * Finish/stabilize/document office importer + doc splitter/
> management
> - Asiri
> * Finish/stabilize/document webdav - Asiri
> * Finish/stabilize/document REST support - Fabio
> * Finish/stabilize/document new blog application - Sergiu/
> Guillaume
> * Continue UI improvements (ex: new treeview, new search
> interface,
> full list to be defined) - JV/Ecaterina/Guillaume
> * Fix search using lucene plugin - ????
> * Finish XE French translations - JV/Guillaume
> * Fix other bugs (watchlist, page names with special chars, etc) -
> All
> * Refactoring of apps to use more of SSX - Jerome?
>
> Note: I don't think we can commit to have a new skin system or a
> new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
>
> WDYT?
>
> Thanks
> -Vincent
>
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
25 Mar
25 Mar
11:16 a.m.
On Mar 20, 2009, at 6:33 PM, Vincent Massol wrote:
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another
stability level (I'm thinking about the old wysiwyg editor which
could be said to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8
to ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9
final with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is
released we'll continue releasing bugfix versions of 1.9.x from time
to time but we'll advise people to switch to 2.x. I propose we keep
support for the old 1.0 syntax (either using the old code or using
the 1.0 --> 2.0 syntax converter) for 1 year. This is the time we
have to make our existing users switch to the new syntax. Note that
with the automatic converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Thomas is the main person who'll be working on this but I'll help
where needed since there are 50+ issues scheduled for 1.9. I'll try to
help working on issues blocking other devs.
* Finish/stabilize/document new wysiwyg editor -
Marius/Anca
* Finish/stabilize/document office importer + doc splitter/
management - Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
* I'll also work on one issue dear to Ludovic: active installs
tracking (see my other mail)
* As usual I'll spend most of my time to try to ensure overall quality/
deadline respect/coordination between people
* I won't work on a specific domain for this release, instead trying
to help wherever I can on low hanging fruits.
Thanks
-Vincent
Note: I don't think we can commit to have a new
skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
Thanks
-Vincent
11:33 a.m.
Vincent Massol wrote:
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
I'll be working on the new UI for the Wysiwyg editor, XWIKI-3429 and XWIKI-3435
(XWIKI-3431 is part of the new UI too, but I don't think it will be done in this
timeframe) along with finishing the general wizard to use for all Wysiwyg
chained actions.
Happy coding,
Anca Luca
* Finish/stabilize/document office importer + doc
splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
Note: I don't think we can commit to have a new skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:42 a.m.
On Fri, Mar 20, 2009 at 6:33 PM, Vincent Massol <vincent(a)massol.net> wrote:
Roadmap for XE 1.9
================
Content proposal:
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
I'll give a hand on the WYSIWYG by working on:
- Page / attachment picker for the link dialog
- Image picker for the image dialog
- New WYSIWYG/Wiki tabs + fullscreen
- Table plugin improvements and bugfix
* Continue UI improvements (ex: new treeview, new
search interface,
full list to be defined) - JV/Ecaterina/Guillaume
I'll:
- Integrate the new Treeview in AllDocs
- Make a proposal about how to include the dashboard in space homes
- Fix dashboard bugs
- Review/commit patches submitted by Caty
- Try to fix toucan's bug on linux to be able to drop Albatross
- Work on http://jira.xwiki.org/jira/browse/XWIKI-800
* Finish XE French translations - JV/Guillaume
I'd like to apply http://jira.xwiki.org/jira/browse/XWIKI-2617
I'll handle the patch for watchlist, I'll also commit the last updates
before M2 since we've agreed that it is the role of the release
manager. Sergiu would you mind to review/apply the patch submitted by
Thomas for the blog application
http://jira.xwiki.org/jira/browse/XABLOG-19 ?
* Fix other bugs (watchlist, page names with special
chars, etc) - All
I'll fix the issues we have with Watchlist (mostly in virtual mode).
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
+1.
JV.
5:17 p.m.
Hi,
On Wed, Mar 25, 2009 at 11:42 AM, Jean-Vincent Drean <jean-vincent(a)drean.org
Really big +1 from TomE. I'll continue doing IE6 testing as much as I can to
help on this front.
Here are the other things that we will try to address in the course of the
release. Stuff that cannot be done in time will be pushed to a later
release. Note: we might be able to get some time from Raluca in the course
of the release, she would help by integrating Caty's work in XE. Raluca
would need assistance from Jérome / JV to have her work committed.
- New search interface -> reflexion + interface work is already done,
integration to be done by JV or Jérome or Raluca
- Improved Stats (requested by a customer) -> my work to define what we
need, maybe a little work from Caty to provide a better look for stats
widgets, a dev work for the velocity + API part (maybe Ludovic ?)
- Improved user profile (asked by StephaneB) -> my work to gather
requirements and see what's needed to make our user profile more generic /
configurable, Caty's work for its look & feel, Raluca for integration.
- Smaller tasks such as moving some menus and/or actions around -> JV &
me
I need to review the full French wiki to hunt mistakes. I'll work with JV to
fix them.
Note: I submitted the blog translation patch, TomE only created the issue.
Sergiu, I'd be glad if you could apply it.
wrote:
On Fri, Mar 20, 2009 at 6:33 PM, Vincent Massol <vincent(a)massol.net>
wrote: >
I talked about the roadmap with project managers, here's their feedback and
mine:
Roadmap for XE
1.9 > ================ >
Content proposal: > > * Finish/stabilize/document new wysiwyg editor -
Marius/Anca
I'll give a hand on the WYSIWYG by working on: - Page / attachment picker
for the link dialog - Image picker for the image dialog - New
WYSIWYG/Wiki tabs + fullscreen - Table plugin improvements and bugfix * Continue UI
improvements (ex: new treeview, new search interface, >
full list to be defined)
- JV/Ecaterina/Guillaume I'll: - Integrate the
new Treeview in AllDocs - Make a proposal about how to include the
dashboard in space homes - Fix dashboard bugs - Review/commit patches
submitted by Caty - Try to fix toucan's bug on linux to be able to drop
Albatross - Work on http://jira.xwiki.org/jira/browse/XWIKI-800 * Finish XE
French translations - JV/Guillaume I'd like to apply
http://jira.xwiki.org/jira/browse/XWIKI-2617 I'll handle the patch for
watchlist, I'll also commit the last updates before M2 since we've agreed
that it is the role of the release manager. Sergiu would you mind to
review/apply the patch submitted by Thomas for the blog application
http://jira.xwiki.org/jira/browse/XABLOG-19 ? > * Fix other bugs (watchlist, page names with
special chars, etc) - All I'll fix the issues we have with Watchlist (mostly in
virtual mode).
Fixing the watchlist gets a big +1 from StefB, specifically:
- Improving the look of the default email sent
- Making the watchlist work in XEM
Proposed Dates: > * 1.9M1: 6 April > * 1.9M2: 4
May > * 1.9RC1: 18 May > *
1.9RC2/Final: 1 June > * 2.0: 15 June > +1.
JV.
+1
Guillaume
_______________________________________________ devs
mailing list
devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://guillaumelerouge.com/
11:46 a.m.
Vincent Massol wrote:
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
I would like to add:
* Captcha integration and configuration UI from the administration
(regiter + comment actions)
* Velocity / Script macro bridge for rendering 2.0 (possibly wiki markup
macros too, to be discussed) - as mentioned in my previous mail
+1
Note: I don't think we can commit to have a new
skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:55 a.m.
On Fri, Mar 20, 2009 at 18:33, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
100% (as much as possible) of my time is dedicated on the general
making new rendering stable and support new syntax in all existing API
and all current use cases in which xwiki 1.0 syntax is used.
* Finish/stabilize/document new wysiwyg editor -
Marius/Anca
* Finish/stabilize/document office importer + doc splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
Note: I don't think we can commit to have a new skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
12:43 p.m.
On Wed, Mar 25, 2009 at 11:55, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
--
Thomas Mortagne
On Fri, Mar 20, 2009 at 18:33, Vincent Massol
<vincent(a)massol.net> wrote:
forgot the +1
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
100% (as much as possible) of my time is dedicated on the general
making new rendering stable and support new syntax in all existing API
and all current use cases in which xwiki 1.0 syntax is used.
> * Finish/stabilize/document new wysiwyg editor - Marius/Anca
> * Finish/stabilize/document office importer + doc splitter/management
> - Asiri
> * Finish/stabilize/document webdav - Asiri
> * Finish/stabilize/document REST support - Fabio
> * Finish/stabilize/document new blog application - Sergiu/Guillaume
> * Continue UI improvements (ex: new treeview, new search interface,
> full list to be defined) - JV/Ecaterina/Guillaume
> * Fix search using lucene plugin - ????
> * Finish XE French translations - JV/Guillaume
> * Fix other bugs (watchlist, page names with special chars, etc) - All
> * Refactoring of apps to use more of SSX - Jerome?
>
> Note: I don't think we can commit to have a new skin system or a new
> skin in place for the 1.9 timeframe.
>
> Proposed Dates:
> * 1.9M1: 6 April
> * 1.9M2: 4 May
> * 1.9RC1: 18 May
> * 1.9RC2/Final: 1 June
> * 2.0: 15 June
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Thomas Mortagne
12:33 p.m.
Vincent Massol wrote:
Hi devs,
XE 2.0
=====
We've had discussion about XE 2.0 in the past. I think now is the
right time to release it and we should prepare to do so. Two reasons;
1) We've had a lot of new features (new rendering, new wysiwyg,
webdav, REST, office import, usability improvements, etc) added
recently in 1.8 and this alone warrants calling it 2.0. The new
rendering and new wysiwyg could be set as default in XE 2.0.
2) XE 1.0 marked a stability level. XE 2.0 will mark another stability
level (I'm thinking about the old wysiwyg editor which could be said
to be stable...)
3) It's been almost exactly 2 years since we released XE 1.0, it's
high time for a major release.
However since we still have a bit of work to fully finish the new
rendering and new wysiwyg and since we want user feedback from 1.8 to
ensure we get a rock solid 2.0 release I propose to have a XE 1.9
release before the XE 2.0 (which would be a promotion of XE 1.9 final
with the config change to have new syntax/wysiwyg as defaults).
The other advantage of releasing XE 2.0 is that we want to start the
maintenance period for the old rendering/old wysiwyg as early as
possible to get new people to use the new system. Once 2.0 is released
we'll continue releasing bugfix versions of 1.9.x from time to time
but we'll advise people to switch to 2.x. I propose we keep support
for the old 1.0 syntax (either using the old code or using the 1.0 -->
2.0 syntax converter) for 1 year. This is the time we have to make our
existing users switch to the new syntax. Note that with the automatic
converters it shouldn't be something too difficult.
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document new rendering - Thomas/Vincent
* Finish/stabilize/document new wysiwyg editor - Marius/Anca
For 1.8.1 and 1.9M1 I'm going to work mainly on:
* fixing bugs
* improving the macro support:
** add more input controls (XWIKI-3436)
** improve the way macro/parameter description is shown (XWIKI-3438)
* implementing the features needed on Curriki:
** font and color management (XWIKI-3441, XWIKI-3442)
** remove formatting (XWIKI-3439)
For 1.9M2 [and 1.8.x] I'm going to work mainly on:
* fixing remaining bugs
* continue improving the macro support:
** use Anca's dialog wizard for the macro UI (XWIKI-3434)
** display macros by category/library (XWIKI-3437)
* profiling to improve the speed of the editor
* hopefully:
** add support for marking text as monospace (XWIKI-3188)
** upgrade to GWT 1.6
** edit object properties that accept rich text (XWIKI-3275)
** support for verbatim, definition list and quote
** support for custom parameters
* Finish/stabilize/document office importer + doc
splitter/management
- Asiri
* Finish/stabilize/document webdav - Asiri
* Finish/stabilize/document REST support - Fabio
* Finish/stabilize/document new blog application - Sergiu/Guillaume
* Continue UI improvements (ex: new treeview, new search interface,
full list to be defined) - JV/Ecaterina/Guillaume
* Fix search using lucene plugin - ????
* Finish XE French translations - JV/Guillaume
* Fix other bugs (watchlist, page names with special chars, etc) - All
* Refactoring of apps to use more of SSX - Jerome?
Note: I don't think we can commit to have a new skin system or a new
skin in place for the 1.9 timeframe.
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
WDYT?
+1
Thanks,
Marius
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:52 p.m.
On Mar 20, 2009, at 6:33 PM, Vincent Massol wrote:
Roadmap for XE 1.9
================
General:It's a stabilization release meaning we must resist putting
new things in it and fix what doesn't work well enough.
Content proposal:
* Finish/stabilize/document REST support - Fabio
+1
I've been communicating with the RESTlet team in order to fix some
bugs and they are almost there so the idea is also to improve the set
of the provided representations (currently only application/xml,
application/json)
Add some resources as we see fit (there are already requests from JV).
Proposed Dates:
* 1.9M1: 6 April
* 1.9M2: 4 May
* 1.9RC1: 18 May
* 1.9RC2/Final: 1 June
* 2.0: 15 June
+1
Cheers,
Fabio
5707
days inactive
5712
days old
20 comments
11 participants
participants (11)
-
Anca Paula Luca -
Fabio Mancinelli -
Guillaume Lerouge -
Jean-Vincent Drean -
Jerome Velociter -
Ludovic Dubost -
Marius Dumitru Florea -
Niels Mayer -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol