Re: [Zope-Coders] Proposal: put i18n into 2.6
We had to wait this long, why not wait for a bit longer. I just hope it doesn't give some the excuse to drag it on more. That was one of the things I loved about Zope was Release Early/often mantra. Now with the 2.6 dabacle lasting over 3 months. This better not happen again people :-) We already know how some people get uneasy when I project starts to languish for months. It only hurts the opensource movement. Peace, -- James From: "Florent Guillaume" <fg@nuxeo.com>
As Jim said, "If we want to get this into 2.6, we need to move quickly."
I want it in. It's so amazingly useful, that I want it. 2.6 is moving so slow anyway, that I don't see it as a big problem. Best Regards Lennart Regebro, Torped http://www.easypublisher.com/ Peace, -- James I am a Washington State Citizen. Spamming this Email Address may be against Washington State Law Chapter 19.86, and 19.190 RCW. http://www.wa.gov/ago/junkemail/protect.html _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx
From: "James Johnson" <tacomabbs@hotmail.com>
We had to wait this long, why not wait for a bit longer. I just hope it doesn't give some the excuse to drag it on more. That was one of the things I loved about Zope was Release Early/often mantra. Now with the 2.6 dabacle lasting over 3 months. This better not happen again people :-) We already know how some people get uneasy when I project starts to languish for months. It only hurts the opensource movement.
True. But in true XP fashion, each release could simply contain the features that are finished. And if this i18n is finished, then it can be included. I think that would also prevent some drag, because now we decided on which features should be included, and several of them wasn't finished. Best Regards Lennart Regebro, Torped http://www.easypublisher.com/
Lennart Regebro wrote:
True. But in true XP fashion, each release could simply contain the features that are finished. And if this i18n is finished, then it can be included. I think that would also prevent some drag, because now we decided on which features should be included, and several of them wasn't finished.
This I agree with. cheers, Chris
Truth is that the Zope code has done anything but languish in the last few months. Unfortunately most people are bound by our release cycle, which has given that impression. As for i18n in 2.6, The Zope Pope gave the nod, so I consider it a done deal, assuming it gets checked in. -Casey On Wednesday 18 September 2002 11:43 am, James Johnson wrote:
We had to wait this long, why not wait for a bit longer. I just hope it doesn't give some the excuse to drag it on more. That was one of the things I loved about Zope was Release Early/often mantra. Now with the 2.6 dabacle lasting over 3 months. This better not happen again people :-) We already know how some people get uneasy when I project starts to languish for months. It only hurts the opensource movement.
Peace, -- James
From: "Florent Guillaume" <fg@nuxeo.com>
As Jim said, "If we want to get this into 2.6, we need to move quickly."
I want it in. It's so amazingly useful, that I want it. 2.6 is moving so slow anyway, that I don't see it as a big problem.
Best Regards
Lennart Regebro, Torped http://www.easypublisher.com/
Peace, -- James I am a Washington State Citizen. Spamming this Email Address may be against Washington State Law Chapter 19.86, and 19.190 RCW. http://www.wa.gov/ago/junkemail/protect.html
participants (4)
-
Casey Duncan -
Chris Withers -
James Johnson -
Lennart Regebro