Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <[EMAIL PROTECTED]> writes:
If Andre is serious about cleaning up the dialog, backporting patches
will soon be impossible anyway. So, my opinion is that we should not
do the renaming in 1.5.x.
+1
One solution to limit the trouble is to deliver 1.6.0 sooner. This
means no XML, trunk is in feature freeze and only cleanup is allowed.
Deciding this 2 months after the previous major release is quite
short, even if we decide to be fester than previously.
Why? If we decide this now, we could aim for an 1.6 release in two or
three months.
Code needs time
to mature, IMO.
Exactly. And the new code will not mature if we put XML now because
nobody will be able to use trunk for real work anymore.
And with such a policy, unicode would never have been
done, and xml will not be done.
My opinion is that unicode happened way too late in the 1.5 devel cycle.
As I said before, if XML is mostly ready (say 3/4) put it in now or
forget about it.
Abdel.