[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Intent to NMU of help for an l10n upload of movabletype-opensource to fix pending po-debconf l10n bugs



Dear Debian maintainer,

The movabletype-opensource Debian package, which you are the maintainer of, has
pending bug report(s) which include translation updates or fixes
for po-debconf, namely bug number 475871 (and maybe other similar bugs).

Even though this bug is quite recent, the release of Debian is not that
far and an opportunity should be taken to not only fix
that l10n bug, but also get more translations for your package.

I have the intention, as part of a more general action of the Debian
i18n Task Force to build and possibly upload a non-maintainer upload
for movabletype-opensource in order to fix this as well as all pending translations
for the debconf templates.

Of course, as you seem pretty active on that package, an upload by you
would also be OK...as long as it allows a round of translation
updates.

Such changes are always harmless, which explains why I safely consider
building NMU's for such issues even though they're obviously non critical.

The schedule for the NMU (in case it happens, that is if you agree with it
or if I don't receive any answer in 14 days) is roughly the following:

 Thursday, May 22, 2008   : send this notice
 Thursday, June 05, 2008       : post a NMU announcement to debian-i18n with you
                 (maintainer) CC'ed
 Sunday, June 15, 2008       : deadline for receiving translation updates
 Monday, June 16, 2008       : build the package and upload it to DELAYED/2-day
                 send the NMU patch to the BTS
 Wednesday, June 18, 2008       : NMU reaches incoming

If you intent to upload yourself, please discuss with me. I propose
handling a translation update round and I can handle it myself for you.
That will just require a few days.

In case I upload an NMU, I will subscribe to the Package Tracking System for
movabletype-opensource and follow its life for 60 days after my NMU in order to fix
any issue potentially introduced by my upload.

Let me know, as soon as possible, if you have any kind of objection to this
process.

If you'd rather do the fix yourself, I will of course leave the package
alone. Same if you have reasons not to do the update now.

-- 


Attachment: signature.asc
Description: Digital signature


Reply to: