[FFmpeg-devel] FFmpeg 0.6 status update

[Reinhard Tartler]

On Sun, Aug 01, 2010 at 05:30:58 (EDT), V?ctor Paesa wrote:

> Hi Reinhard,
>
> I saw your commit talking about 0.6.1. There are a couple of items pending:

thanks for reminding me here.

> On Wed, Jun 23, 2010 at 16:22, Reinhard Tartler wrote:
>> On Wed, Jun 23, 2010 at 00:28:01 (CEST), V?ctor Paesa wrote:
>>
>>> Hi,
>>>
>>> On 2010-06-22, Reinhard Tartler wrote:
>>>> On Sun, Jun 20, 2010 at 23:22:00 (CEST), Reinhard Tartler wrote:
>>>>
>>>>> From the comments in this thread I conclude:
>>>>>
>>>>> ?- the website announcement should be prepared before release in the
>>>>> ? ?release branch
>>>>>
>>>>> ?- the translation shall be included there as well before release
>>>>>
>>>>> ?- we should ask for review of the release notes before relase on
>>>>> ? ?ffmpeg-devel
>>>>>
>>>>
>>>> Translations of the announcement and the release notes (currently only
>>>> .it) can now be found in the releases/ directory. ?In case I missed one,
>>>> please send it to me directly, I'll install it then.
>>>
>>> I attach the ffmpeg-0.6.release.es
>>
>> installed
>>
>>> There is some redundance between announcement and release notes, by the way.
>>
>> yes, I wonder solve this by writing the release notes in a way that we
>> can put them as news entry straight on the website for the next releases.
>>
>>>> I have to admit that I've messed up the translations for 0.6. I promise
>>>> to do better for the next release(s).
>
> How will this work for 0.6.1? Should we commit the translation to the
> svn branch?

Yes, I think that would be easiest. They don't do harm in the tarballs,
and this way we can also review the website announcement.


>>> These are the file types I get for the announcements in the /releases directory:
>>>
>>> ffmpeg-0.6.ANNOUNCE ? ? ? ? ? text/plain; charset=utf-8
>>> ffmpeg-0.6.ANNOUNCE.es ? ? ? ?application/ecmascript
>>> ffmpeg-0.6.ANNOUNCE.fr ? ? ? ?text/plain; charset=utf-8
>>> ffmpeg-0.6.ANNOUNCE.pl ? ? ? ?text/x-perl
>>> ffmpeg-0.6.ANNOUNCE.se ? ? ? ?text/plain; charset=utf-8
>>>
>>> Could the type be text/plain UTF-8 for all of them?
>>
>> Can the admins comment on that? (BCC'ed). Would adding '.txt' to each
>> filename be a good solution for that?
>
> What's the decision on the '.txt' suffix? I'd say go for it, as there is
> no opposition.

agreed.

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4