Hi sajolida,
thank you for your time filing those tickets :)
Unfortunately I can't look at them closely until Monday because I'm
traveling, so please forgive me if the answers to my questions below
could be easily found by examining their details.
> - A beta release in time for 1.8 (December 15). The assistant would be
> advertised in the release notes, maybe tweet about it and send a mail to
> tails-testers. That's tracked by #8590 and subtasks.
I will certainly try, but I'm not sure I can fix all those issues by
then because I'm gonna attend Mozilla's December work-week in Orlando
(AKA "Mozlando"), from 7 to 12, and I'm pretty sure I won't own the
golden share on my time, there.
However, if you set some kind of priority on them, I'll start from the
highest attempting to fix as much as possible, always aiming for the
full package of course.
>
> - A final release in time for or before (January 26). The assistant
> would then replace the current installation instructions and be linked
> from the current "Download" button on the website (renamed "Install").
> That's tracked by #8592 and subtasks.
That's definitely feasible.
> So by December 15 we would need to have:
>
> - The Debian and Ubuntu packages ready in backports and PPA. So we can
> do the beta with the final instructions for them.
What does it mean from a logistics standpoint for me? Do I just need to
commit my fixes to my repository and set the "Ready for QA" flag on the
bugs, ir is there some further step I need to take for the things going
in there place for your release, and what the actual deadlines?
> - A version of the extension uploaded to addons.mozilla.org so we can
> point to it instead of maone.net.
That can be done, with the aforementioned caveat.
-- G
On 27/11/2015 16:37, sajolida wrote:
> Hi,
>
> I'm putting tails-ux in copy but the implications of these mostly affect
> development work so please answer on tails-dev.
>
> Last week-end we did intensive testing of the current prototype for the
> Installation Assistant. We spent 18 hours testing the whole process with
> 16 people and many findings came out of it.
>
> You can check the rainbow table [1] if you want to see our findings.
> Today I'll also write a more specific email about the work left to be
> done on the extension.
>
> [1]:
> https://labs.riseup.net/code/attachments/download/1070/ux-testing-20151120.ods
>
> Then we decided on the release schedule for the whole thing. And I want
> to check with Girgio and u whether that's fine with them. We thought
> about doing:
>
> - A beta release in time for 1.8 (December 15). The assistant would be
> advertised in the release notes, maybe tweet about it and send a mail to
> tails-testers. That's tracked by #8590 and subtasks.
>
> - A final release in time for or before (January 26). The assistant
> would then replace the current installation instructions and be linked
> from the current "Download" button on the website (renamed "Install").
> That's tracked by #8592 and subtasks.
>
> So by December 15 we would need to have:
>
> - The Debian and Ubuntu packages ready in backports and PPA. So we can
> do the beta with the final instructions for them.
> - A version of the extension uploaded to addons.mozilla.org so we can
> point to it instead of maone.net.
>
> Does that seems feasible to you?
> _______________________________________________
> Tails-dev mailing list
> Tails-dev@???
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an empty email to Tails-dev-unsubscribe@???.
--
Giorgio Maone
https://maone.net
