A plan is better than no plan, so here is my suggestion:
The Pike 7.3 CVS is forked into a new development version, 7.5, next saturday (14/9). At the same time the 7.3 tree is renamed to 7.4. All API/language design changes and the like must be completed before then. Only bug fixes and release related changes will be accepted after the CVS shuffle.
Bugs: 3022 BMP fails on 64bit machines (was this a WONTFIX? If so the test should be rewritten) FreeBSD sometimes fails to build post_modules and to run popen. Some machines has problems running Crypto.sha correctly. MS Windows fails spectaculary with dynamic loading. Turn it off?
Design issues: There must be a semicolon added after implicit lambdas.
What's missing/wrong?
Not as such, but it complicates the port a bit since it's the same code. What the encode/decode fixes in 7.2 do is to abstract the dumping of the symbol tables in programs in a platform independent way. Together with the non-native byte code they make program dumps architecture independent. They also improves the error checking when dumped programs are loaded and e.g. the programs they inherit have changed, and they are a step towards making dumped programs less dependent on the exact storage structure of inherited programs.
/ Martin Stjernholm, Roxen IS
Previous text:
I also think we should focus 7.4 first and put it in subversion later. Regarding the cvs browser, I won't get it svn-ready until the release. A pike with svn bindings @ pelix would probably get the code librarian svn support there quicker, though. :-) Especially after it has the fs API. IIRC the RA API could be fun too, but it's possible I would have to run the indexer locally at all times anyway, unless the svn guys thought about that use case.
/ Johan Sundström (nu även i Gottfridsberg!)
Previous text:
pike-devel@lists.lysator.liu.se