Re: Release?

I think you mean beyond 2.10. We've already given out 2.10 for previous versions. Backtracking now would be *bad*. If it was my choice I would give them 2.12 and a list of what works. It is not like giving them 2.12 disables a bunch of 2.8 functions. It just adds to what they might want to use. More is always better. Yeah that makes the project look incomplete but that is because /it is/ incomplete. I probably would have called the alpha 2.0.0, beta 2.0.1, and this 2.0.2. At this rate it will never be 100% as GTK grows at a rate faster than PHP-GTK does, and calling a 2.0.0 with 2 year old GTK version makes you feel like that day you were chatting with a beautiful woman online just to find out she was a balding 45 year old man (...). My third suggestion would be to call this PHP-GTK2-2.0.0(delta|gamma|whatever) instead. The 'alpha' was never a 'real' 'alpha' and the 'beta' was never really a 'real' 'beta' anyway. And then just continue on with that trend still PHP6 *i make giggle* Also in the Unix world, all new systems worth their effort come with the latest software (even Solaris with Blastwave :o !), so we'll just be causing a divide in operating systems. I took the 2.6 precompiled Unix versions down off my site, and 2.8 is coming down soon too. -- Bob Majdak Jr KateOS Rofflecopter Pilot http://www.kateos.org Anant Narayanan wrote: >> This might be a silly question... but if I recall right the last build >> Elizabeth did was Unzip and go all self contained on Windows, did not >> interact with the system GTK... so... why not just /give/ them Gtk >> 2.12. Then everyone will be using a PHP-GTK2 with max features for max >> lawlz without borking the system. > > Giving them GTK 2.12 would be a bad move as not even 10% of the new > classes have been implemented. We shouldn't go beyond 2.8. > > Cheers, > Anant >