9 Jan
2012
9 Jan
'12
9:30 a.m.
On Jan 9, 2012, at 12:10 AM, Sergiu Dumitriu wrote:
Hi devs,
Since a long time ago, the xwiki/1.0 syntax has been deprecated in favor of the new
rendering engine and the 2.x syntaxes, but this has never been declared deprecated
formally. We should:
* mark the syntax as deprecated in the UI (like 2.1 was marked experimental in the syntax
choice dropdown)
* deprecate classes and methods that deal only with the old syntax
* push more for migrating all documents to the 2.1 syntax; the biggest troublemaker is
the statistics application
Here's my +1.
+1
We should also decide on a timeline for the complete
removal of the 1.0 syntax. Is that something we want to do? Provided we manage to migrate
all the official documents and some major contributed applications during the 4.x cycle,
is XWiki 5.0 a good target?
IMO we can do this any time in 4.x. I also agree that the first step is to extract the 1.0
syntax rendering into its own module ASAP (note: we need to keep velocity parsing in core
since it's still needed by templates and translations). Then when this is done and
when we don't have any XWiki Syntax 1.0 content in our default pages we release that
module on extensions.xwiki.org as an optional module.
Thanks
-Vincent
We should package the support for xwiki/1.0 as an
optional extension installable using the extension manager, so that people can upgrade
from older versions. Or we could package just a syntax migrator that can be used for an
automatic conversion to a newer syntax, without actually providing rendering support for
it.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/