I was writing on something like that before christmas:
With Pike 7.4 bottled, what new flavours and colours might the Pike product dept. have planned for Pike 7.6? Planned is perhaps not quite the word when we don't intend to do the acutal work for most action points. Wishlist is more correct, and not without a slight seasonal touch.
- Replace the Crypto module with Nettle. Niels Möller has done some attempts and should be encouraged to continue.
- Rewrite the I/O stuff. Per Hedbor has some architectural ideas that he hopefully will share in a digestable form that will be inspiring enough for some people to dig into this big and delicate task. Unfortunately I'm not that hopeful that it will happen though.
- GTK 2 support. Per Hedbor has begun a rewrite of PiGTK and since the API deprecation pace of GTK isn't as high as it used to be, it might be ready while it still is possible to link to a recent GTK.
- IPv6 support made a quick appearance in Pike 7.3 but caused to much breakage on AutoBuild machines. With Xenofarm it should be much easier to diagnose and fix these problems. Note that all code that deals with IP numbers, sunch as protocol modules, will have to be reviewed and updated before we can say Pike is IPv6 compliant.
Then I had a train to catch... (And I didn't check with Per if he really had a rewrite idea for the I/O, but he hinted it half a year ago or so). I can dicrectly add that a well thought through system for external modules should be added before Pike 7.6 is released.
Looking at Pike management the single most wanted issue is to install an issue tracker on the Pike site. I don't have time for it, but unless Johan Sundström has a hidden agenda (pun intended) he should be able to pull it off before February.
/ Martin Nilsson (bygger parser
Previous text:
2003-01-06 23:00: Subject: Inconsistency.
That said, is there a roadmap for what the future Pike 7.6 will be? I.e any plans, ideas, TODO's for Pike 7.5 before the next stable branch?
/ David Hedbor