Hi Regan,
On Oct 24, 2008, at 10:52 PM, Regan Gill wrote:
Hello XWiki Team,
I have installed XWiki Enterprise to use for my company's internal
collaboration and documentation; I liked it especially for its UI
which
is far superior to other extendable wikis. While adding components and
customizing it I have noticed that there is a tendency to change the
software without much concern for backward compatibility. For example
the macro syntax changes with 1.6 makes multiple macros that were
previously written incompatible (I was particularly interested in the
Jira one). I am concerned that if I want to upgrade at some point, the
customizations I have made using the published API will not work and
cause heartache.
Maintaining backward compatibility is not necessarily easy, but I am
curious whether there is a philosophy of weighing new features higher
than supporting existing ones. This would help me know what to
expect in
regards to how much maintenance work I would need to put in over the
wiki's lifespan.
Our philosophy has always been to maintain backward compatibility as
much as possible. I'm not sure where you've seen that it's not the
case. The new syntax and the new rendering are not breaking backward
compatibility in any manner. Quite the opposite. We're now supporting
several syntaxes (XWiki Syntax 1.0 which is the current syntax, XWiki
Syntax 2.0 which is the new syntax, Confluence, Mediawiki, Creole, etc).
Let us know if you find any backward compatibility issues since that
would be a bug.
Thanks
-Vincent