Re: [Tails-dev] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule
sajolida wrote (01 Dec 2015 16:30:32 GMT) : > I'll have to document how to check whether you are running > testing or sid and that might be the funny part. /etc/os-release and /etc/debian_version should help :) ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule
Giorgio Maone:
> On 30/11/2015 20:32, sajolida wrote:
>> Giorgio Maone:
>>> thank you for your time filing those tickets :)
>>>
>>> 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.
>>
>> Ok, so I set elevated prio on:
>>
>> - #10686: Network disconnection shouldn't make download fail in DAVE
>> - #10678: Prevent DAVE from reloading the page every 10s
>>
>> And lowered prio on:
>>
>> - #10685: Change in IDF should reset DAVE (← needs a confirmation)
>
> Confirmed, DAVE currently fetches the IDF (and therefore resets itself)
> every time either the browser starts, or the extension gets
> updated/installed/enabled after being disabled.
Ok, so let's stick to low priority for the beta then.
> Therefore this ticket is basically about forcing the IDF to be reloaded
> every time you load the UI page, or even more often (e.g. by setting a
> timer which reloads it every 3 minutes or so if the UI is currently
> shown), correct?
There might be some ambiguity on what you call "reloading the IDF", so
I'll elaborate just a bit.
The IDF should definitely be fetched again each time the user reloads
the page and the extension should check if the IDF changed. If the IDF
changed, then the state of the extension should be reset ("verified"
should go to "download"). Imagine people who don't close their browser
for days, they might download the ISO image one day, give up in the
middle of the installing instructions and reopen the page 5 days later.
We should ask them to download a fresh ISO in case the IDF changed.
But we shouldn't ask these same people to download again if they reload
the page but the IDF is still the same. During the UX tests, quite a few
people switched from one installation scenario to the another, and
having DAVE still marked as "downloaded and verified" even if you switch
scenario is definitely helpful: people don't have to download and verify
the ISO again to try another scenario.
Now, I'm not sure what should happen if the IDF changes *in the middle
of the download* (you close your tab and open it again) but that's a
corner case and I'm fine with having DAVE validate this download. These
people are unlucky anyway...
Regarding "setting a timer which reloads it every 3 minutes or so" that
would be helpful for people who might keep the tab open for days with an
ISO image already downloaded; as these people are not reloading the
page. But then, how we transmit this information to them might be
complicated. Changing the state of the verification without them
reloading the page feels wrong. I'd say this is a corner case as well,
and I'm fine with not modifying the validation we gave them already.
Ah, and for people who might open the page and not start the download
immediately, then maybe the IDF should be checked upon when actually
starting the download. I don't know when you're doing that exactly in
the process right now.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule
intrigeri: > (I'm stealing parts of the "Tails Installer in Debian" work from > u for the rest of the year.) > > sajolida wrote (27 Nov 2015 15:37:56 GMT) : >> 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. >> [...] >> Does that seems feasible to you? > > For Debian: I re-uploaded the package yesterday to fix some issues > (#8557), and it takes quite some time to go from the NEW queue to > backports (for details, see the answer I wrote last time you asked). > So best case we'll have the package in sid and maybe testing, but my > advice is that you should really not count on it being accepted in > jessie-backports by December 15. So I guess we'll document that it's only available in testing and sid for the beta. I'll have to document how to check whether you are running testing or sid and that might be the funny part. > In a PPA: yes (I'll let u double-check and commit to it herself > though). Cool! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule
On 30/11/2015 20:32, sajolida wrote: > Giorgio Maone: >> 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. > I don't think that there is any new information in these tickets, > outside from what we already discussed on the list. Now that I could read them no, indeed :) >>> - 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. > Ok, so we'll try to react quickly this week (before the 7) if you have > questions or are blocked. Then we'll leave you alone from the 7th to the > 12th. Perfect. >> 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. > Ok, so I set elevated prio on: > > - #10686: Network disconnection shouldn't make download fail in DAVE > - #10678: Prevent DAVE from reloading the page every 10s > > And lowered prio on: > > - #10685: Change in IDF should reset DAVE (← needs a confirmation) Confirmed, DAVE currently fetches the IDF (and therefore resets itself) every time either the browser starts, or the extension gets updated/installed/enabled after being disabled. Therefore this ticket is basically about forcing the IDF to be reloaded every time you load the UI page, or even more often (e.g. by setting a timer which reloads it every 3 minutes or so if the UI is currently shown), correct? > Just to clarify, my bullet point referred to the work on Tails > Installer done with intrigeri and u, so there's no implication for you > I think. But yes, once you committed a fix in your repo you should > mark your tickets as "Ready for QA" and assigned to me (or tchou). > Regarding the deadline, as none of our work goes into the actual ISO > image, our deadline is only to be ready when 1.5 is announced. That's > on Tuesday 15 late CET. I think that our work should be done on Monday > 14 so I can have some time on Tuesday to integrate everything on the > website, make sure everything works as expected, write the release > notes, etc. Roger > Regarding your schedule, when would you do the process to upload to AMO? > Before the 7? Between the 7 and the 12? Most likely between the 8 and the 11, when I'll be working shoulder-to-shoulder with the AMO admin themselves and help it to be approved immediately. -- G ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule
Hi, (I'm stealing parts of the "Tails Installer in Debian" work from u for the rest of the year.) sajolida wrote (27 Nov 2015 15:37:56 GMT) : > 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. > [...] > Does that seems feasible to you? For Debian: I re-uploaded the package yesterday to fix some issues (#8557), and it takes quite some time to go from the NEW queue to backports (for details, see the answer I wrote last time you asked). So best case we'll have the package in sid and maybe testing, but my advice is that you should really not count on it being accepted in jessie-backports by December 15. In a PPA: yes (I'll let u double-check and commit to it herself though). Cheers, -- intrigeri ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule
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@boum.org > https://mailman.boum.org/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. -- Giorgio Maone https://maone.net ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Installation Assistant (+ ISO Verification Extension + Tails Install in Debian): release schedule
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@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
