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

Announce of the upcoming NMU for the atlas package



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dear maintainer of atlas and Debian translators,

Christian Perrier sent a notice to the maintainer of the atlas Debian
package, mentioning the status of pending localization bug reports in
the BTS.

He announced the intent to build and possibly upload a non-maintainer
upload for this package in order to fix all its long-time pending
localisation bugs (and these bugs only, unless there is a fix ready for
bug #288172), but atlas FTBFS on his machine.

Since then, he didn't get any objection from the package maintainer and
then I will start the second phase of the process as it still FTBS on
Christian's machine.

If needed, I will notify the translators for languages for which the
translation is still incomplete without update sent to the BTS so that
they have a chance to send updates on time.

The package is currently translated to: fr nl

The following translations exist but are incomplete: NONE

Other translators also have the opportunity of creating a translation
in their language for this package. Please go to
http://www.debian.org/intl/l10n/po-debconf/pot and pick up the
relevant templates.pot.gz file. Once completed, please send it
directly to me so that I incorporate it in the package being built.

The deadline for receiving updates and new translations is fixed to
30 jan 2005.

Of course, if in the meantime the maintainer objects to this process,
I will stop it and send him/her all updates I have received.

Otherwise, the following will happen (or already have):
- -Christian  : send the first intent to NMU notice to
~             the package maintainer
- -24 jan 2005: this announcement
- -30 jan 2005: deadline for receiving translation updates
- -2 feb 2005 : build the package and upload it to DELAYED/2-day
~                send the NMU patch to the BTS
- -4 feb 2005 : NMU uploaded to incoming
- -5 feb 2005 : NMU enters unstable

As you may see, the NMUed package will be built and then uploaded to
DELAYED/2-day, giving the maintainer two more days for reacting to the
NMU.

I will then subscribe to the package PTS and follow its life for 60
days after my NMU in order to fix any issue potentially introduced by
my upload.

Of course the NMU patch will also be sent to the BTS.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFB9O+A5UTeB5t8Mo0RAijRAKCRikRDY99jQ7k7rxmUM9RHtOEc/wCgqR97
dnAwSs10uuCkMSclBGnTtHg=
=wlMp
-----END PGP SIGNATURE-----



Reply to: