Hi, On Wed, Sep 3, 2008 at 6:28 AM, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > Hi folks -- > > In a few minutes we'll be announcing a fix for a security problem in > Django; the fix will be part of the 1.0rc1 release that's coming, um > any moment now. > > Unfortunately, we had to make a string change (one new string) as part > of this release. I know, it's really too late to be doing this, what > with the 1.0 final release schedule for tomorrow or the day after. > However, we had to follow best practices in security reporting and > keep this quiet until now to give package maintainers time to get > ready for a new release.
First of all, I don't blame you at all. I just want to clarify. I've run django-admin for making new .po file with revision 8889, and noticed that there is no new message at all. There is only one fuzzy message. Is that what you expect? Regards, -- Takashi Matsuo > I'm really very sorry about the timing, and I'll take all the blame > for any translator who can't hit 100% in 1.0 because of me! > > Thanks, > > Jacob Kaplan-Moss > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django I18N" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Django-I18N?hl=en -~----------~----~----~----~------~----~------~--~---
