Re: [Tails-dev] Please help coordinate the work on Tails 3.0
Hi, I've just made a pass on the remaining 3.0 tickets, postponed some, and adjusted priorities here and there. So now would be a good time to sanity-check your (updated) plate, if not done yet :) 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] Please help coordinate the work on Tails 3.0
Hi, intrigeri: > Almost all big changes we want to see in 3.0 are done, or close to be. > We'll release 3.0~beta4 on Wednesday, and likely a first release > candidate around May 20, after which only minimal fixes for important > problems will go in. That's still the plan. The 3.0 milestone has 76 open tickets, which doesn't seem entirely realistic to me: let's fix that! Please have a look now at *your* Tails 3.0 tickets, and think: if you can handle them by the end of May, fine. If there are some you think you will not be able to address by the end of May, then please clarify your plans on Redmine ASAP so anonym and I have time to take over if we feel they are release blockers. Bonus points if you drop me a line privately once you've gone through this, so I know how to interpret any lack of action on Redmine :) Thanks a lot in advance! 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] Please help coordinate the work on Tails 3.0
intrigeri: > sajolida: >> intrigeri: >>> tl;dr: please clarify by the end of April if you can handle your 3.0 >>> and priority >= Elevated Redmine tickets by May 15. > >> I had a look at my tickets. I quite clearly won't be able to tackle all >> my 3.0 and 3.0~rc1 ticket >= Elevated by May 15. Otherwise I would have >> to spend nearly all of my Tails time on this and not on the many other >> "not so urgent" stuff and that wouldn't be wise. > > Thanks for this update! > >> But most of them are documentation tickets and I think it's fine to >> tackle them after May 15. > > Well, ideally I would like us to give translators a month to update > their stuff. But I understand we're not living in an ideal world, so > well, fair enough, surely the doc update can be completed later. > So I would suggest: > > * prioritize doc updates that affect the code (e.g. the new Greeter's >doc) or critical UX paths (e.g. discovering what's Tails, >downloading, installing, upgrading, troubleshooting and basic >usage) over doc about advanced or rarely useful topics (e.g. >#12376, #12378); Right. I would add "reviewing each others work" to the list of what should get our attention in priority. Or at least it's a good share of my work towards 3.0 :) > * communicate this to translators ASAP so they can get ready to >deal with whatever timeline you think is realistic on your side. Agreed as well. What I could do is still send a call for translation around May 15th, listing stuff that can already be updated. Trying to be careful about not living tickets open that will affect these same bits again before the release. I created #12498 to track this. >> I spotted three tickets that are not pure doc and that I will prioritize >> (in this order) and should get done before May 15: > >> - #12368: Design UX for migrating databases to KeePassX 2 >> - #11962: Update installation/upgrade process/tools/doc for amd64 >> - #12441: Impossible to copy text from vim into X > >> And another ticket that could be handled by someone else, maybe you if >> you feel its safer, but it shouldn't much work either so I'll very >> probably be able to tackle it if prioritized wisely: > >> - #11573: Update po_translatable_pages for Tails 3.0 > >> How does it sound? > > Sounds good. You might want to use the new 3.0~rc1 target version to > encode this in Redmine. I didn't do that so far but I should and I'll try :) ___ 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] Please help coordinate the work on Tails 3.0
Hi, sajolida: > intrigeri: >> tl;dr: please clarify by the end of April if you can handle your 3.0 >> and priority >= Elevated Redmine tickets by May 15. > I had a look at my tickets. I quite clearly won't be able to tackle all > my 3.0 and 3.0~rc1 ticket >= Elevated by May 15. Otherwise I would have > to spend nearly all of my Tails time on this and not on the many other > "not so urgent" stuff and that wouldn't be wise. Thanks for this update! > But most of them are documentation tickets and I think it's fine to > tackle them after May 15. Well, ideally I would like us to give translators a month to update their stuff. But I understand we're not living in an ideal world, so well, fair enough, surely the doc update can be completed later. So I would suggest: * prioritize doc updates that affect the code (e.g. the new Greeter's doc) or critical UX paths (e.g. discovering what's Tails, downloading, installing, upgrading, troubleshooting and basic usage) over doc about advanced or rarely useful topics (e.g. #12376, #12378); * communicate this to translators ASAP so they can get ready to deal with whatever timeline you think is realistic on your side. > I spotted three tickets that are not pure doc and that I will prioritize > (in this order) and should get done before May 15: > - #12368: Design UX for migrating databases to KeePassX 2 > - #11962: Update installation/upgrade process/tools/doc for amd64 > - #12441: Impossible to copy text from vim into X > And another ticket that could be handled by someone else, maybe you if > you feel its safer, but it shouldn't much work either so I'll very > probably be able to tackle it if prioritized wisely: > - #11573: Update po_translatable_pages for Tails 3.0 > How does it sound? Sounds good. You might want to use the new 3.0~rc1 target version to encode this in Redmine. 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] Please help coordinate the work on Tails 3.0
intrigeri: > tl;dr: please clarify by the end of April if you can handle your 3.0 > and priority >= Elevated Redmine tickets by May 15. I had a look at my tickets. I quite clearly won't be able to tackle all my 3.0 and 3.0~rc1 ticket >= Elevated by May 15. Otherwise I would have to spend nearly all of my Tails time on this and not on the many other "not so urgent" stuff and that wouldn't be wise. But most of them are documentation tickets and I think it's fine to tackle them after May 15. I spotted three tickets that are not pure doc and that I will prioritize (in this order) and should get done before May 15: - #12368: Design UX for migrating databases to KeePassX 2 - #11962: Update installation/upgrade process/tools/doc for amd64 - #12441: Impossible to copy text from vim into X And another ticket that could be handled by someone else, maybe you if you feel its safer, but it shouldn't much work either so I'll very probably be able to tackle it if prioritized wisely: - #11573: Update po_translatable_pages for Tails 3.0 How does it sound? ___ 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] Please help coordinate the work on Tails 3.0
Hi, intrigeri: > tl;dr: please clarify by the end of April if you can handle your 3.0 > and priority >= Elevated Redmine tickets by May 15. I will handle the rc one (fontconfig in reproducible ISO), and the 3.0 one is about the sponsor page. It's doable too. Cheers u. ___ 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] Please help coordinate the work on Tails 3.0
Hi, intrigeri: > tl;dr: please clarify by the end of April if you can handle your 3.0 > and priority >= Elevated Redmine tickets by May 15. I've created a 3.0~rc1 target version, so these tickets are on one of these two Redmine views: https://labs.riseup.net/code/projects/tails/issues?query_id=242 https://labs.riseup.net/code/projects/tails/issues?query_id=198 Feel free to use the new 3.0~rc1 target version to better express your plans :) 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] Please help coordinate the work on Tails 3.0
Hi, tl;dr: please clarify by the end of April if you can handle your 3.0 and priority >= Elevated Redmine tickets by May 15. Almost all big changes we want to see in 3.0 are done, or close to be. We'll release 3.0~beta4 on Wednesday, and likely a first release candidate around May 20, after which only minimal fixes for important problems will go in. So far we shared the work very nicely among a number of people, and it's been amazing. Now, the release will happen in 2 months, and anonym and I are personally responsible for putting it in good shape, so I'd like to know more precisely what the two of us will have to deal with ourselves. So, please have a look now at *your* Tails 3.0 tickets with priority Elevated or higher, and think: if you can handle them by May 15, fine. If there are some you think you will not be able to address by May 15, then please de-assign you or at least clarify your plans on Redmine. Bonus points if you drop me a line privately once you've gone through this, so I know how to interpret any lack of action on Redmine :) Thanks a lot in advance! 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.
