[xwiki-devs] question about integration/roadmap of the new modular architecture/rendering engine etc...
Hello, I have been working for some time compiling my own snapshot XWikiEnterprise 1.5 (I was following the trunk in fact) but I have stopped following the trunk in order to test some things... Apparently now the version is 1.6... Before looking directly in the code with my own eyes, I prefer asking a few questions about all the new features (modular architecture, new rendering, new macros etc...): Are they integrated in the last available tags? (the modular architecture has appeared long time ago but it's not the default archi yet) Does it break any compatibility? Do you still use the old implementations as the default one? When do you intend to replace the old archi with the new one? Do you have an idea of the roadmap for this? Is version 2.0 the version when the old implementations will disappear? I need to have such information in order to know if I go on upgrading using the trunk because it brings some bug corrections without breaking any existing things? or do I use a tag version to have a stable and fixed platform? I don't fear using new versions and examining bugs and even correcting them as long as they don't destroy my database? Best regards Pascal
Hi Pascal, On Aug 3, 2008, at 12:06 PM, Pascal Voitot wrote:
Hello, I have been working for some time compiling my own snapshot XWikiEnterprise 1.5 (I was following the trunk in fact) but I have stopped following the trunk in order to test some things... Apparently now the version is 1.6... Before looking directly in the code with my own eyes, I prefer asking a few questions about all the new features (modular architecture, new rendering, new macros etc...): Are they integrated in the last available tags? (the modular architecture has appeared long time ago but it's not the default archi yet)
It's been integrated a long time ago but we've decided to do integration rather than a big bang meaning we've started doing it slowly one piece at a time. Right now there are the following new parts in 1.6 which use the new component based architecture: - new velocity module - new rendering modules - new cache modules - new observation modules - new container/context modules - new query manager and probably some more.
Does it break any compatibility?
No.
Do you still use the old implementations as the default one?
For what? For the rendering yes.
When do you intend to replace the old archi with the new one? Do you have an idea of the roadmap for this? Is version 2.0 the version when the old implementations will disappear?
There's no such roadmap. We're replacing bit by bit. Right now we're working on 3 parts: - new rendering - new wysiwyg - new storage with jcr/query manager Future steps are: - write the new model - write the new storage
I need to have such information in order to know if I go on upgrading using the trunk because it brings some bug corrections without breaking any existing things?
No it doesn't break anything normally.
or do I use a tag version to have a stable and fixed platform? I don't fear using new versions and examining bugs and even correcting them as long as they don't destroy my database?
Don't worry about that. Note: the new rendering introduces a new column in the DB for documents: the syntax id. the old syntax is used when this field is empty, null or contains "xwiki/1.0". Thanks -Vincent
participants (2)
-
Pascal Voitot -
Vincent Massol