Whit Blauvelt schrieb:
> Will the 1.3.9 to 1.4.0 upgrade path be trivial, or will there be enough
> work in upgrading between the two to make it worth waiting for 1.4.0 before
> implementing a fairly complex project given that 1.4.0 (and beyond) should
> be the target for it?
index.php configs moved to config/config.ini
(finished, in current CVS, some problems occur from time to time)
the PrettyWiki detection is much more stable now (hope it stays so),
the include code for pear is kind of problematic, because it leaves the
decision to the user (no problems yet reported, but I am sure there will
be),
adodb is completely new (finished, in current CVS, no problems since two
weeks anymore),
page permissions will be usable (not yet).
Some bugs will be fixed, and some new bugs will be introduced (hopefully
not)
But before 1.4.0 we will bring out 1.3.10, to test the latest fixes and
to gain some confidence in the stability.
Carsten thought about full utf-8 support, but I think we will postpone
this to the 1.5.x branch.
Currently we cannot switch between single-byte charsets and multi-byte
charsets. Either you define utf-8 and convert all docs to utf-8 (chinese
and japanese already are), or you define for example latin-1 and cannot
display japanese and chinese together with the single-byte charsets.
regex attributes might have to be fixed for utf-8, dynamic conversion
will have be to be done, and so on.
Currently I work on
* support for older php versions (on 4.0.5 and 4.0.4-pl1 it runs very
unstable) and the php-5.0 branch,
* strange dba problems with certain php versions (< 4.1 and > 4.3, with
locking and session_write_close problems), and
* a weird pcre problem which only appears on the loaded sf.net server
(php-4.1.2)
This might lead to some needed optimizations for the InlineParser.
If this cannot be fixed sooner or later, we will have to revert to the
old parser code, without the memory optimizations and without inlined
tightened plugins.
e.g. "* <small><?plugin MostPopular></small>", or
inlined "This site runs the PhpWiki <?plugin SystemInfo version?> version."
will then not be supported.
But if my analysis is true, adding more Interwiki urls will also break
the parser sooner or later, which is not really an option.
Besides that a lot of bugs appear and disappear on the sf.net tracker,
which is good sign.
I also expect some adodb pgsql problems with transactions, and mysqli
and mysqlt requests.
You can try out the current CVS code by yourself. I don't expect it to
break. Only on very very weird setups it breaks.
--
Reini Urban
http://phpwiki.sf.net/
|
