Re: [Tails-dev] Release versioning
Hi, sajolida wrote (27 Nov 2015 12:58:31 GMT) : > Please review 095e86b and 145da9a. Thanks! Added 09d9cde and 255589c on top. > Anything else? The only missing bit that I can think of is: there are quite a few occurrences of version numbers that need updating in a few internal Git repositories of ours. 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] Release versioning
intrigeri: > sajolida wrote (27 Nov 2015 12:58:31 GMT) : >> Please review 095e86b and 145da9a. > > Thanks! Added 09d9cde and 255589c on top. > >> Anything else? > > The only missing bit that I can think of is: there are quite a few > occurrences of version numbers that need updating in a few internal > Git repositories of ours. Sure, I didn't think about that. So I updated: - master (841af4e) - internal (90ad3ac) - accounting (8750ec7) I didn't updated the UDFs as I didn't want to break anything. Can you do it? For example: - upgrade/v1/Tails/1.9/i386/alpha/upgrades.yml I also couldn't update the various reports that we already sent to sponsors mentioning 1.9 and others. So I gave then a conversion table in 1a753fb. ___ 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] [RFC] WhisperBack for frontdesk
On our roadmap for 2016 we put some minor improvements to WhisperBack regarding languages (#9799) and OpenPGP keys (#9800). We started working on this with Alan and here the blueprint we came up with: https://tails.boum.org/blueprint/whisperback_for_frontdesk/ I'm putting tails-ux in copy so they know this discussion is happening, but I'm actually more interested in feedback from tails-dev regarding the privacy issues we're raising in the blueprint. I'm also putting tails-support-private in copy as they should be the first interested in this. So please everybody, answer on tails-dev. ___ 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] Release versioning
Hi, sajolida wrote (30 Nov 2015 16:39:04 GMT) : > So I updated: > - master (841af4e) > - internal (90ad3ac) > - accounting (8750ec7) Thanks! I'll check these one of these days. I think fundraising also has some, no? > I didn't updated the UDFs as I didn't want to break anything. Can you do > it? For example: > - upgrade/v1/Tails/1.9/i386/alpha/upgrades.yml I don't think there's anything to update there; if you think differently, please tell me what you think should be updated and why and then I or anonym can do it. > I also couldn't update the various reports that we already sent to > sponsors mentioning 1.9 and others. So I gave then a conversion table in > 1a753fb. I'll check this one soonish too. 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, (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.
[Tails-dev] Tails contributors meeting: Thursday December 03
ls contributors meeting is scheduled for: Thursday 03 December #tails-dev on irc.oftc.net 9 pm in Paris 8 pm in London 3 pm in New-York 12 pm in San Francisco Everyone interested in contributing to Tails is welcome! Feel free to propose and prepare discussion topics. Either: - Raise them in this thread so that others can ask details and prepare the discussion too. - Update the blueprint of the agenda: https://tails.boum.org/blueprint/monthly_meeting/ - Make sure that the discussion tickets that you want to treat during the meeting are well detailed on Redmine. If you want to get involved but don't know yet how, please introduce yourself during the meeting, and be sure to tell us what you are interested in. The meeting might not be the most adequate time and place to properly introduce newcomers to the development process, but at least it should be a fine place to know each others, and schedule a better suited event. ___ 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.
