7 Apr
2008
7 Apr
'08
10:15 a.m.
From my server architect's point of view, I see
XWiki as a still young and
very active project...
Not yet fully stable in its perimeter and final aims: lots of things are
still opened and being studied.
For the time being, new releases don't only involve bug correction but new
functional and design features. There is still this euphoric progression in
the project and this is what I was looking for when I chose XWiki. New ideas
are coming every day and they are integrated progressively but it means new
releases bring sometimes new feature that, as a user, you want to integrate
for sure. But if there are some regressions as Vincent explained, the eager
user can be deceived.
As a developer, I can also see new crucial modifications of the core such
as the component design which is very important for me as a potential XWiki
plugin/app/core developer and logically, I know this kind of evolution
always brings lots of unforeseen regressions.
Anyway, I don't find the releases are too fast or too slow... I trust the
xwiki team to solve the small regression problems :)
I'm not against faster releases... Just keep identifying important,
meaningful and stable releases.
Considering the config files, good thing to put them outside the WAR. You
could even let the hibernate.cfg.xml (from the installation point of view,
knowing hibernate is behind all of this is not important) in the war and put
some configuration parameters linked to it in the xwiki.cfg
regards
Pascal
On 4/6/08, Squirrel <squirrel(a)shadowgmail.com> wrote:
On Sun, Apr 6, 2008 at 2:59 PM, Vincent Massol <vincent(a)massol.net> wrote:
Right so you agree that faster release cycles are better as otherwise
that means no new stuff for a very long time ;)
Hehe, owned.
What do you find hard to upgrade xwiki?
Let me think over that again... ;-)
Sure but it's not because there are updates that you *have* to
upgrade... The user still decides when he
upgrades.
Agreed. Hmmm...maybe I'm just not sure about how much customization I can
do
without breaking anything (after the next update/upgrade)...the
customization I do (on macros, classes and so forth), are they stored in
files or in the DB? I guess in the DB, that's what confuses me as a
Joomla!
user...I guess I have to read more in the docs...
Cheers,
Squirrel
PS: I really like the way the Xwiki team talks to the community!
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs