Re: [Tails-project] writing the release notes for 1.3

sajolida:
> sajolida:
>> anonym:
>>> On 19/02/15 18:05, sajolida wrote:
>>>> sajolida:
>>>> I'm merely proposing to try a process to collectively improve on the
>>>> phrasing, being a bit more verbose and user oriented. As RM are pretty
>>>> busy with many other things, and as many other contributors and testers
>>>> would bring their own view on the changes made and how to explain them
>>>> to a board spectrum of users.
>>>
>>> Sounds great! Would this include RC's release notes?
>>
>> I don't want to overload us with tons of extra work. So as a start I'd
>> like to work on the official notes of major releases only. Since they
>> are the ones which are really bringing in new things.
>>
>>> However, on a more technical note, I think it may be hard for you to
>>> know what to write in it since the changelog generally is prepared quite
>>> late in the release process, and if you are gonna try to keep track of
>>> what's going on you'd duplicate the work of the RM to a large extent.
>>> However, there's a solution!
>>
>> When I wrote about that the other day I was a bit in a rush, but I think
>> that the idea is to actually build something *on top of* the work that
>> you are already doing. For example, for major releases there's already
>> have a draft from you when the RC is put out, no? So we would work on a
>> best effort basis to improve on that work and make it more fancy.
>>
>> My secret plan is to have more people than me work on that. Because if
>> it's just extra work for me, then it's no fun and probably won't be a
>> success.
>
> I had a closer look at this today and pushed 7dfeefa..a1f50e4. That made
> me realize that what I want is just to have more eyes looking at the
> work that you're doing already and propose small improvements on top of it.

Ah, and I didn't need to reconfigure Pidgin to use the Tor Browser as
suggested in the notes. It's configured to use `sensible-browser` which
works fine for me in 1.3~rc1 with persistence.