Re: [Tails-dev] Post-1.3.2 ticket assignments and postponements

2015-04-03 Thread intrigeri
Hi, anonym wrote (01 Apr 2015 21:55:02 GMT) : BTW, when releasing, 36 tickets were still open and in need of being either postponed or made into a Hole in the roof. It sounds like a pretty high number to me (of which I was contributing quite a bit!) and I'm wondering if we need to start to

Re: [Tails-dev] Post-1.3.2 ticket assignments and postponements

2015-04-03 Thread intrigeri
Hi Adam, Adam Burns wrote (02 Apr 2015 07:10:26 GMT) : I caused the ticket 8986 to be raised and recently joined the list to not only follow up, but also see where I can help out. Woohoo :) It's my understanding that the issue is the current default Claws configuration of the Drafts /

Re: [Tails-dev] Post-1.3.2 ticket assignments and postponements

2015-04-03 Thread Adam Burns
On Friday 03 April 2015 11:48:27 intrigeri wrote: Hi intrigi, It's also my belief that a solution be documented as soon as possible to publicize to existing users on existing versions the risk and how to mitigate it. Fully agreed. I believe BitingBird has added notes to this effect on

[Tails-dev] Post-1.3.2 ticket assignments and postponements

2015-04-01 Thread anonym
Hi, Tails 1.3.2 has been released but it's Release Manager view is still not empty: https://labs.riseup.net/code/projects/tails/issues?query_id=175 BTW, when releasing, 36 tickets were still open and in need of being either postponed or made into a Hole in the roof. It sounds like a pretty