Hello Martijn,

I'm also in favour of keeping them indefinitely.

Marginally related - also please keep history of who sent/reviewed the
translation indefinitely (currently this
info is lost after the package review is finished).

Regards,
~~helix84

On Wed, Jun 15, 2011 at 13:56, Joe Dalton <[email protected]> wrote:
> Hi Martijn, I would expect it to be kept indefinitely (or as long as the 
> package exists). It should be possible to add or change the information next 
> time it shows up.
> bye
> Joe
>
>
> --- Den ons 15/6/11 skrev Martijn van Oosterhout <[email protected]>:
>
>> Fra: Martijn van Oosterhout <[email protected]>
>> Emne: Re: What about DDTSS do you (dis)like?
>> Til: "Joe Dalton" <[email protected]>
>> Cc: "Debian I18n" <[email protected]>
>> Dato: onsdag 15. juni 2011 00.05
>> On 14 June 2011 22:55, Joe Dalton
>> <[email protected]>
>> wrote:
>> > Danish team would appreciate a function which saves
>> the comments.
>> >
>> > An example:
>> > We are working on crash
>> > http://ddtp.debian.net/ddtss/index.cgi/da/forreview/crash?1307901577
>> >
>> > and had a small discussion about a certain word. We
>> found some reference (the link) and some other informations.
>> This information is lost then the translation gets its final
>> review. So we cannot see this information then the
>> translation gets fuzzy and we have to update it (after a
>> change in the English description).
>>
>> That's a good one. Some kind of post submission log. Would
>> you expect
>> this to be kept indefinitely, just to the next time this
>> package comes
>> up, or maybe just for a few weeks?
>>
>> Have a nice day,
>> --
>> Martijn van Oosterhout <[email protected]>
>> http://svana.org/kleptog/
>>
>
>
> --
> To UNSUBSCRIBE, email to [email protected]
> with a subject of "unsubscribe". Trouble? Contact [email protected]
> Archive: http://lists.debian.org/[email protected]
>
>


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: 
http://lists.debian.org/[email protected]

Reply via email to