Re: Break string freeze for GDM 2.20

2008-03-01 Thread Claude Paroz
Le vendredi 29 février 2008 à 15:37 -0600, Brian Cameron a écrit :
 I would like to request a string freeze break for GDM 2.20.  Since
 GDM 2.22 was not approved for inclusion in GNOME 2.22, I would like
 to get some fixes into GDM 2.20 that would be nice to address, but
 affect strings.  I plan to do a new GDM 2.20 release sometime in
 the near future so that people can get the latest bug fixes when
 they upgrade to GNOME 2.22.
 
 Can I get approval to fix the following bugs with the attached
 patches?
 
 - The documentation needs to be updated to explain that the Custom
Widgetry interface broke slightly due to moving away from using
vicious-extensions and moving towards gkeyfile.
 
 - Bug 477881, fix GDM to honor the default password character
rather than hardcoding it to the '*' character
 
http://bugzilla.gnome.org/show_bug.cgi?id=477881

As this contains some security implication, I would say this is worth
committing, as if we don't do it upstream, distros will patch
downstream...
Approval 1 of 2 for i18n.

 - Improve tooltip in gdmgreeter
 
http://bugzilla.gnome.org/show_bug.cgi?id=389734
 
I notice that, by accident, I committed the 2nd patch (tt.diff)
to GDM 2.20.3.  If I don't get approval, I can back this out
of the next release.

This one seems minor to me. But if the first change is approved, I think
we could also let one more string.

Claude


___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Break string freeze for GDM 2.20

2008-03-01 Thread Deniz Koçak
On Sat, Mar 1, 2008 at 12:26 PM, Claude Paroz [EMAIL PROTECTED] wrote:
 Le vendredi 29 février 2008 à 15:37 -0600, Brian Cameron a écrit :

  I would like to request a string freeze break for GDM 2.20.  Since
   GDM 2.22 was not approved for inclusion in GNOME 2.22, I would like
   to get some fixes into GDM 2.20 that would be nice to address, but
   affect strings.  I plan to do a new GDM 2.20 release sometime in
   the near future so that people can get the latest bug fixes when
   they upgrade to GNOME 2.22.
  
   Can I get approval to fix the following bugs with the attached
   patches?
  
   - The documentation needs to be updated to explain that the Custom
  Widgetry interface broke slightly due to moving away from using
  vicious-extensions and moving towards gkeyfile.
  
   - Bug 477881, fix GDM to honor the default password character
  rather than hardcoding it to the '*' character
  
  http://bugzilla.gnome.org/show_bug.cgi?id=477881

  As this contains some security implication, I would say this is worth
  committing, as if we don't do it upstream, distros will patch
  downstream...
  Approval 1 of 2 for i18n.


   - Improve tooltip in gdmgreeter
  
  http://bugzilla.gnome.org/show_bug.cgi?id=389734
  
  I notice that, by accident, I committed the 2nd patch (tt.diff)
  to GDM 2.20.3.  If I don't get approval, I can back this out
  of the next release.

  This one seems minor to me. But if the first change is approved, I think
  we could also let one more string.

  Claude

Approval 2 of 2.
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n


Re: Break string freeze for GDM 2.20

2008-03-01 Thread Brian Cameron

Deniz/Claude:

Thanks, the changes are now committed.  So now the docs and i18n team
can help to translate these small changes.  I think it is nice to get
these fixes into GDM 2.20.

Brian


  As this contains some security implication, I would say this is worth
  committing, as if we don't do it upstream, distros will patch
  downstream...
  Approval 1 of 2 for i18n.


   - Improve tooltip in gdmgreeter
  
  http://bugzilla.gnome.org/show_bug.cgi?id=389734
  
  I notice that, by accident, I committed the 2nd patch (tt.diff)
  to GDM 2.20.3.  If I don't get approval, I can back this out
  of the next release.

  This one seems minor to me. But if the first change is approved, I think
  we could also let one more string.

I agree this change is minor, but I wanted to bundle it with the other
changes.  As you say, allowing one more string to fix another bug.  Why
not?  Glad you agree.

Thanks again,

Brian
___
gnome-i18n mailing list
gnome-i18n@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-i18n