Re: [Tails-dev] [Tails-project] Call for feedback: *test* migration to GitLab
Hi, On 07/05/2020 11:24, intrigeri wrote: > Hi, > > I mistyped the tails-dev@ email address when I sent this on April 25, > so fully quoting. > > Apart of that, below there's a gentle "ping" for nodens, and nothing more. And of course when I replied on the 27th, I did "reply all" without checking… I'll reproduce the replies to make it easier to follow this discussion. > intrigeri (2020-04-25): >> [moving back the discussion to tails-dev@, and this time, setting >> Reply-To via technical means and not merely via a social request.] Ooops. Missed the request in the message body, sorry. >> nodens (2020-04-16): We have added you as a "participant" to every GitLab issue that you were watching on Redmine. On Redmine, there was a way to get a list of the issues you were watching. At the moment, there's no equivalent feature on our GitLab. Does this break your workflow? If it does, this could go on the list of things we'll try to fix. >>> >>> Actually, it does, a bit. My contributions are far & between, so I rely >>> on the "watch" list to remember what I wanted to have an eye on, when I >>> have the time or am in the mood for some Tails stuff. >> >> Thank you, this is useful. >> >>> It's not the end of the world, if I get notified of changes on any issue >>> I was watching. But it's gonna be impractical to find those unless I >>> actually remember them - and even then, I'll need to remember some >>> specific keywords to search for them. >> >> I understand this would fix the problem for issues you were already >> watching on Redmine: on every issue you were watching, as part of the >> migration process, we add a :star: reaction in your name. Then, you >> can list those issues with the "My-reaction = :star:" filter (the UI >> actually display nice emojis). >> >> But you'll still have to manually track, somehow, the issues you'll >> start participating in on GitLab; you could use the same trick, or use >> your activity view. >> >> Do you confirm this would solve the problem you've reported? > > Ping? Yes! I use this workflow on github.com and gitlab.com projects already, so it feels natural. Thanks. Cheers, -- nodens ___ Tails-dev mailing list Tails-dev@boum.org https://www.autistici.org/mailman/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Release schedule for Tails 3.5
Hi! On 04/01/2018 19:02, anonym wrote: > Testers, please let me know: > > * if you are available on 2018-01-22, late CET yep > > * if you are available on 2018-01-23, morning to afternoon, CET. Possibly early morning, and a bit around noon, if needed. Cheers, -- nodens ___ 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] Tails 3.1 release schedule
On 27/06/2017 11:18, bertagaz wrote: > Hi, > > As it sometimes happen, I'll be the 3.1 release manager. I've finally settled > on a schedule for it, here it is: > > * 2017-08-04, noon: all branches targeting Tails 3.1 must be merged > > * 2017-08-05: Import Tor Browser 7.0.2, build and upload Tails 3.1 > > * 2017-08-06: Start testing Tails 3.1 > > * 2017-08-08: Release 3.1 (Firefox 52.3) > > Manual testers, please tell me (privately if you prefer) your availability to > test this release. Given it will be a summer release and people may not be > that > available for testing, I'd appreciate to know in advance if none of the usual > testers will be able to take care of that so that I can organize. > I'll be at Debconf, but I guess I can find time for some manual tests while there if there is not enough other testers :) Cheers ___ 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 schedule for Tails 2.7
Hi ! Le 05/11/2016 à 17:20, bertagaz a écrit : > Usual testers, please let me know (privately) about your availability > for testing the ISO on: > > - 2016-11-13: if I'm able to build and upload the ISO soonish, testing > it could start that day. Evening > - 2016-11-14: all day Depending on where I am, I can spend morning or afternoon on it, and most of the evening. There may be shifts. > - 2016-11-15: until 6pm CEST, in case we did not complete the test > suite the day before Not available > > Note that I'll be travelling to the sprint on 2016-11-14, so testers > will have to self-organize a bit while I'm offline during that day. signature.asc Description: OpenPGP digital signature ___ 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] Meeting: our Tails/Jessie progress and plans
Le 18 décembre 2014 17:39:00 CET, u u...@451f.org a écrit : hi, intrigeri: I propose we have another meeting in a month, shortly after the next release, e.g. on January 16. As I see it, the main goal, this time, would be to see how we're doing wrt. getting the fixes we need into Jessie, and re-prioritize anything that is lagging behind on that front. anonym, Alan, others? (e.g. U., kytv, bertagaz and nodens could all be very helpful on the Debian side of things :) ok, then let's have a meeting on th 16th indeed to see what needs to be done. Works for me, unless I already have a work meeting at the same time. Cheers, -- nodens ___ 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.
