Re: [Tails-dev] Release schedule for Tails 3.9
Hi! > intrigeri: >> - August 15: feature freeze > >>Everything you want to see in Tails 3.9 must be merged into our >>devel branch by 17:00 CEST that day. > > The path was not the sweetest RM'ing hike I've ever experienced but > somehow we got there! All the major branches that had to make it into > 3.9~rc1 are now merged \o/ Amazing ! :) ___ 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 3.9
sajolida: > intrigeri: >>> - August 18-30: small, targeted, not too risky fixes may be granted >>>freeze exceptions > I'll need one for the VeraCrypt documentation. I want to update it to > whatever will land in the RC but, If you're referring to the renaming dance: that's been done already :) > depending on how things go with > VeraCrypt regarding the trademark license it might need more adjustment > down the road (ideally, only reverting a commit). Deal! ___ 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 3.9
intrigeri: > intrigeri: >> - August 15: feature freeze > >>Everything you want to see in Tails 3.9 must be merged into our >>devel branch by 17:00 CEST that day. > > The path was not the sweetest RM'ing hike I've ever experienced but > somehow we got there! All the major branches that had to make it into > 3.9~rc1 are now merged \o/ It's also the biggest release since 3.0, so thanks for handling this and congrats for the merge! > Anyone who still has work left to polish or finish for 3.9, please > read or re-read this: > >> - August 18-30: small, targeted, not too risky fixes may be granted >>freeze exceptions I'll need one for the VeraCrypt documentation. I want to update it to whatever will land in the RC but, depending on how things go with VeraCrypt regarding the trademark license it might need more adjustment down the road (ideally, only reverting a commit). -- sajolida ___ 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 3.9
intrigeri: > - August 15: feature freeze >Everything you want to see in Tails 3.9 must be merged into our >devel branch by 17:00 CEST that day. The path was not the sweetest RM'ing hike I've ever experienced but somehow we got there! All the major branches that had to make it into 3.9~rc1 are now merged \o/ Anyone who still has work left to polish or finish for 3.9, please read or re-read this: > - August 18-30: small, targeted, not too risky fixes may be granted >freeze exceptions >Reviewer time will be a very scarce resource during that period so >please anticipate. If you can already guess that you'll need >a bigger freeze exception that does not fit into these rules, talk >to me ASAP. >Please try hard to avoid changing user-visible strings during that >period: I'd like translators to have a couple weeks to do the great >amount of work I'll drop on their plate on August 17, so we release >our fancy new features in 3.9 with the best localization they can >get :) Thanks in advance, happy hacking! -- 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 schedule for Tails 3.9
intrigeri: > sajolida: >> intrigeri: >>> - August 18-30: small, targeted, not too risky fixes may be granted >>>freeze exceptions >> >> Does this apply to documentation fixes? We should be able to finish all >> the doc in time for the RC but I'll give priority to my UI/coding work >> over my documentation work. > > Documentation fixes are user-visible strings, so they are covered by: > >>>Please try hard to avoid changing user-visible strings during that >>>period: I'd like translators to have a couple weeks to do the great >>>amount of work I'll drop on their plate on August 17, so we release >>>our fancy new features in 3.9 with the best localization they can >>>get :) > > … small documentation fixes will be welcome but it won't be a great > time to merge large pieces of new / totally revamped doc. Now, since > there was apparently a misunderstanding on the definition of > "user-visible strings" and it took me 3 weeks to clarify it, I'll be > a bit more flexible than I intended to be when I wrote the message > you're replying to. Doc will be in time for the freeze! -- sajolida ___ 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 3.9
intrigeri: >If all this is very nice but too vague, as a rule of thumb: > - if you're a developer, better submit your large chunks of work by >August 5 and schedule enough time for post-review fixes during >August 5-12 > - if you're a reviewer, please consider scheduling time for >reviews during August 5-15 Reminder: we're now past August 5. Happy hacking & reviewing! ___ 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 3.9
Hi, sajolida: > intrigeri: >> - August 18-30: small, targeted, not too risky fixes may be granted >>freeze exceptions > Does this apply to documentation fixes? We should be able to finish all > the doc in time for the RC but I'll give priority to my UI/coding work > over my documentation work. Documentation fixes are user-visible strings, so they are covered by: >>Please try hard to avoid changing user-visible strings during that >>period: I'd like translators to have a couple weeks to do the great >>amount of work I'll drop on their plate on August 17, so we release >>our fancy new features in 3.9 with the best localization they can >>get :) … small documentation fixes will be welcome but it won't be a great time to merge large pieces of new / totally revamped doc. Now, since there was apparently a misunderstanding on the definition of "user-visible strings" and it took me 3 weeks to clarify it, I'll be a bit more flexible than I intended to be when I wrote the message you're replying to. > I'll be working with Simply Secure on September 3 and traveling on > September 4. So the timing of the release is not optimal for me as a > technical writing (but it's not something new). > I'll try to write the release notes before that and to be available on > September 5 to document last minute known issues. But don't count on me > on September 3-4. OK; maybe add this to #14683 so I find this info when I need it? Thankfully most of the changes should make it into the RC so you'll have quite some time to prepare them in advance. I'm not concerned :) 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 schedule for Tails 3.9
intrigeri: > it's not clear who will be the release manager for Tails 3.9 yet but > we're well into its development cycle and lots of great, intrusive > work has to land in time for that release, so I figured we need at > least a fallback release schedule to provide guidance to everyone who > needs it. Thanks a lot for making plans for that! > - August 15: feature freeze > > - August 18-30: small, targeted, not too risky fixes may be granted >freeze exceptions Does this apply to documentation fixes? We should be able to finish all the doc in time for the RC but I'll give priority to my UI/coding work over my documentation work. >Please try hard to avoid changing user-visible strings during that >period: I'd like translators to have a couple weeks to do the great >amount of work I'll drop on their plate on August 17, so we release >our fancy new features in 3.9 with the best localization they can >get :) This should work. > - September 4: build 3.9 tentative ISO > > - September 5: test and release 3.9 \o/ I'll be working with Simply Secure on September 3 and traveling on September 4. So the timing of the release is not optimal for me as a technical writing (but it's not something new). I'll try to write the release notes before that and to be available on September 5 to document last minute known issues. But don't count on me on September 3-4. -- sajolida ___ 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 3.9
intrigeri, I will be pleased to reserve the time required to test both the 3.8 RC build(s) and tentative release builds. I'm in a position to use each more or less exclusively while testing. Other available distros include Debian and Arch derivatives. alienpup you wrote: > Hi! > > it's not clear who will be the release manager for Tails 3.9 yet but > we're well into its development cycle and lots of great, intrusive > work has to land in time for that release, so I figured we need at > least a fallback release schedule to provide guidance to everyone who > needs it. > > If you're the lead/manager for a team that's affected by this > schedule, please ensure your team-mates are planning their > work accordingly. > > So, in case I end up playing the role of backup RM for Tails 3.9, > here's how it's going to happen: > > - August 15: feature freeze > >Everything you want to see in Tails 3.9 must be merged into our >devel branch by 17:00 CEST that day. > >Particularly for big chunks of work, please do submit them for >review to the foundations team ahead of this date: as the deadline >approaches, quite a few of us will be busy completing their own >work, so let's be excellent to each other by not assuming they're >available for last minute reviews or post-super-late-review fixes. >Better talk to each other in advance to schedule time for these >things ♥ > >If all this is very nice but too vague, as a rule of thumb: > > - if you're a developer, better submit your large chunks of work by >August 5 and schedule enough time for post-review fixes during >August 5-12 > - if you're a reviewer, please consider scheduling time for >reviews during August 5-15 > > - August 16: build tentative 3.9~rc1 > > - August 17: test and release 3.9~rc1 > >→ manual testers: please tell me privately if you can make it. > > - August 18-30: small, targeted, not too risky fixes may be granted >freeze exceptions > >Reviewer time will be a very scarce resource during that period so >please anticipate. If you can already guess that you'll need >a bigger freeze exception that does not fit into these rules, talk >to me ASAP. > >Please try hard to avoid changing user-visible strings during that >period: I'd like translators to have a couple weeks to do the great >amount of work I'll drop on their plate on August 17, so we release >our fancy new features in 3.9 with the best localization they can >get :) > > - September 4: build 3.9 tentative ISO > > - September 5: test and release 3.9 \o/ > >→ manual testers: please tell me privately if you can make it. > > 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 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] Release schedule for Tails 3.9
Hi! it's not clear who will be the release manager for Tails 3.9 yet but we're well into its development cycle and lots of great, intrusive work has to land in time for that release, so I figured we need at least a fallback release schedule to provide guidance to everyone who needs it. If you're the lead/manager for a team that's affected by this schedule, please ensure your team-mates are planning their work accordingly. So, in case I end up playing the role of backup RM for Tails 3.9, here's how it's going to happen: - August 15: feature freeze Everything you want to see in Tails 3.9 must be merged into our devel branch by 17:00 CEST that day. Particularly for big chunks of work, please do submit them for review to the foundations team ahead of this date: as the deadline approaches, quite a few of us will be busy completing their own work, so let's be excellent to each other by not assuming they're available for last minute reviews or post-super-late-review fixes. Better talk to each other in advance to schedule time for these things ♥ If all this is very nice but too vague, as a rule of thumb: - if you're a developer, better submit your large chunks of work by August 5 and schedule enough time for post-review fixes during August 5-12 - if you're a reviewer, please consider scheduling time for reviews during August 5-15 - August 16: build tentative 3.9~rc1 - August 17: test and release 3.9~rc1 → manual testers: please tell me privately if you can make it. - August 18-30: small, targeted, not too risky fixes may be granted freeze exceptions Reviewer time will be a very scarce resource during that period so please anticipate. If you can already guess that you'll need a bigger freeze exception that does not fit into these rules, talk to me ASAP. Please try hard to avoid changing user-visible strings during that period: I'd like translators to have a couple weeks to do the great amount of work I'll drop on their plate on August 17, so we release our fancy new features in 3.9 with the best localization they can get :) - September 4: build 3.9 tentative ISO - September 5: test and release 3.9 \o/ → manual testers: please tell me privately if you can make it. 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.
