Bug#384538: [INTL:ko] Korean iso_3166 update
On Sunday 27 August 2006 02:59, darehanl wrote: Ah, sure. It's Sunjae Park. I thought I had it in there, sorry:-) No problem, thanks for your quick reply. Regards, Tobias -- Tobias Toedter | In the beginning, there was nothing. And God said, Hamburg, Germany | Let there be Light. And there was still nothing, | but you could see a bit better. pgpJKW9cJudWt.pgp Description: PGP signature
Bug#384538: [INTL:ko] Korean iso_3166 update
Ah, sure. It's Sunjae Park. I thought I had it in there, sorry:-) -- Sunjae Park(daréhanl) We choose to go to the moon and do the other things, not because they are easy, but because they are hard. - John F. Kennedy - signature.asc Description: This is a digitally signed message part
Bug#384538: [INTL:ko] Korean iso_3166 update
package iso-codes tag 384538 patch pending thanks Hi, thanks for your contribution, I've applied your patch to the SVN. Would you mind telling us your real name, so we can attribute the copyright correctly to you? Regards, Tobias -- Tobias Toedter | Your lucky number is 3562364958674928. Hamburg, Germany | Watch for it everywhere. pgpmVGFw0wd7G.pgp Description: PGP signature
Bug#384538: [INTL:ko] Korean iso_3166 update
Quoting Tobias Toedter ([EMAIL PROTECTED]): package iso-codes tag 384538 patch pending thanks This is probably a good moment for an upload. There are a lot of pending issues in the SVN, it seems. signature.asc Description: Digital signature
Bug#384538: [INTL:ko] Korean iso_3166 update
On Friday 25 August 2006 11:23, Christian Perrier wrote: This is probably a good moment for an upload. There are a lot of pending issues in the SVN, it seems. Yes, absolutely. I was thinking the same in the last few days. I could prepare a new version on Sunday. After looking at some older uploads, we've had a varying quality of uploads -- sometimes, the package has been uploaded as Debian-native, although this was not reflected in the version number ... therefore, I'd like to do the next upload myself, if you and Alastair don't mind. I would then prepare a short README for the process, so that every uploader can repeat the upload on a step-by-step basis. I think of this as a quality assurance measure, so we don't forget anything during the upload, e.g. tagging the SVN appropriately. :-) Is this alright? Regards, Tobias -- Tobias Toedter | There is no future in time travel. Hamburg, Germany | pgpOCILxL9TwO.pgp Description: PGP signature
Bug#384538: [INTL:ko] Korean iso_3166 update
Quoting Tobias Toedter ([EMAIL PROTECTED]): On Friday 25 August 2006 11:23, Christian Perrier wrote: This is probably a good moment for an upload. There are a lot of pending issues in the SVN, it seems. Yes, absolutely. I was thinking the same in the last few days. I could prepare a new version on Sunday. After looking at some older uploads, we've had a varying quality of uploads -- sometimes, the package has been uploaded as Debian-native, although this was not reflected in the version number ... therefore, I'd like to do the next upload myself, if you and Alastair don't mind. I would then prepare a short README for the process, so that every uploader can repeat the upload on a step-by-step basis. I think of this as a quality assurance measure, so we don't forget anything during the upload, e.g. tagging the SVN appropriately. :-) Is this alright? Completely fine by me. You will just need one of us to upload? If so, just ping me by mail or on IRC. Setting a policy for tagging and the like is a very good idea. I think that the package being either native or non-native is a tricky question. I'd rather see it as non native but that indeed would mean that we also release upstream versions and separate things that pertain to upstream from things that pertain to Debian. If we look at the current SVN version, nearly all uploads should really go in an upstream release indeed. signature.asc Description: Digital signature
Bug#384538: Development of iso-codes (Was: Bug#384538: [INTL:ko] Korean iso_3166 update)
On Friday 25 August 2006 14:30, Christian Perrier wrote: Quoting Tobias Toedter ([EMAIL PROTECTED]): Is this alright? Completely fine by me. You will just need one of us to upload? If so, just ping me by mail or on IRC. Thanks, will do. :-) Setting a policy for tagging and the like is a very good idea. I think that the package being either native or non-native is a tricky question. I'd rather see it as non native but that indeed would mean that we also release upstream versions and separate things that pertain to upstream from things that pertain to Debian. Yes, as I said, the package has sometimes been Debian-native, but most of the time it was separated into upstream and Debian development. I agree with you that it would be preferable to keep things separated. That's one of the things I wanted to discuss with you two. Should we make a clear distinction between Debian and the upstream development? If so, the main change would probably be to keep two separate changelogs ... Apart from that, I've sent a mail to [EMAIL PROTECTED] today and did not receive a copy of it, although I'm subscribed to the PTS. Christian and Alastair, did you receive that mail? If only Alastair did, then this might be the reason why we didn't get notifications about updated translations from the TP. We should then probably use a mailing list as contact address, what do you think? If we look at the current SVN version, nearly all uploads should really go in an upstream release indeed. True. If both of you agree, I'd prepare a proper changelog for the upstream release and cut down the Debian changelog to the Debian-specific parts. (Please drop the bug report from the CCs, it's getting off-topic. Instead, please add Alastair to the CCs.) Regards, Tobias -- Tobias Toedter | Death has been proven to be 99% fatal in laboratory rats. Hamburg, Germany | pgpEK1GtKH633.pgp Description: PGP signature
Bug#384538: [INTL:ko] Korean iso_3166 update
Package: iso-codes Version: N/A Severity: wishlist Tags: l10n iso-codes_iso_3166_ko.po.gz Description: GNU Zip compressed data signature.asc Description: This is a digitally signed message part
