remove gnome-nettool documentation
Can someone please remove the gnome-nettool documentation from the stats? The template is not correct and should be removed to avoid that people start to translate it (contains no gnome-nettool material). Regards, Daniel ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: remove gnome-nettool documentation
Today at 9:53, Daniel Nylander wrote: > Can someone please remove the gnome-nettool documentation from the stats? > > The template is not correct and should be removed to avoid that people > start to translate it (contains no gnome-nettool material). I've reported a bug: http://bugzilla.gnome.org/show_bug.cgi?id=379752 Cheers, Danilo ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
New string on bug-buddy 2.16.1
Hi, I've just commited a change to bug-buddy HEAD (2.16, because it is still not branched) adding a new string. However this string would not be shown in the UI until translated, so it does not break the UI freeze from the end-user point of view. However it would be great to get it translated, so we can deploy bug-buddy 2.16.1 with most localed including this string. Notice that our bugsquad team is complaning a lot about non translated bug reports, so this string addition is in some way _important_ After this, I can only thak you all translators you great work. YOU ROCK! Thanks! Salu2 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
Re: New string on bug-buddy 2.16.1
Ok, my fault. Bug-buddy had been branched for 2.16 and I did that commit to HEAD (2.17). So I've just backported the changes to 2.16, so please update this string on gnome-2-16 branch. Thanks again and sorry for the noise. Salu2 On 11/28/06, Fernando Herrera <[EMAIL PROTECTED]> wrote: > Hi, I've just commited a change to bug-buddy HEAD (2.16, because it is > still not branched) adding a new string. > > However this string would not be shown in the UI until translated, so > it does not break the UI freeze from the end-user point of view. > > However it would be great to get it translated, so we can deploy > bug-buddy 2.16.1 with most localed including this string. Notice that > our bugsquad team is complaning a lot about non translated bug > reports, so this string addition is in some way _important_ > > After this, I can only thak you all translators you great work. YOU ROCK! > > Thanks! > > Salu2 > ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
bug-buddy was branched silently some time ago
Hi, I branched bug-buddy silently some days ago. I cannot remember if my plan was mailing d-d-l and friends in the next morning, but I completely forgot about it. So the hot question: what's expected on 2.17 regarding bug-buddy?. 1) Some polishing of the new UI 2) When no debug symbols are present, dump the crash information into a minidump file and send it to a debug server to create a rich backtrace of the proccess and send it back to bugzilla 3) Implement that debug server code to collect debug info from most common distributions (at least Fedora Core, Debian and OpenSuSE) and to enrich incoming minidumps Two side notes: a) 2) and 3) will introduce a dependencing on google's airbag library and would happen only if that code is ready for out 2.17 schedule. b) I have some code for 3), but what we would need to deploy it is: hardware and bandwith for it. Some time ago I got an email from Intel interested on donating hardware for this purpose, but I lost track about it. Should I ask the Foundation about it? Salu2 ___ gnome-i18n mailing list gnome-i18n@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-i18n
