Hi I'm John Easton product manager forget LeBron, which is that our verify stage today, I'm gonna, spend some time talking about what we plan to deliver. You know upcoming twelve, at six release milestone at a high level. There are two main focus areas for us in the table at six release number one: let's continue to investigate and resolve critical bugs in a giblet on a product and number two is making progress on releasing the beta version of Windows shareowners on github.com.

So let's take a look at the critical issues that we're working to resolve in 12 websites. First up is issue number 432, $7 conflict already in use by container news a sort of experience. This issue have reported that running the same job. Multiple times may result in errors due to container naming conflicts. At this time we have a solid proposal.

That's documented here in the issue, description I expected to deliver a fix for this issue in 1206, the other high priority issue that we've been moving on since 12:00 at 5:00 and need to continue working on at 12:00 that sinks. It's issue number four one more mine, and this is a bug in the gift LeBron acumen in his executor that can result in some jobs too many prematurely but being reported as successfully completed.

The current proposal for twelve that sex is to investigate potential solutions, as documented here in the issue description at least one proposal, its automated and has been recommended by community member looks quite promising. The final critical bug that we'll be working on in 1236 is issue number three, three seven states. This bug is about long-running jobs that have been cancelled in the give them UI, but the one who continues to process the jobs in terms of enhancements and they're important.

My hands will be applying to live in 1236, with extending the get WebRunner custom exactor by exposing the value of an image as an environment variable. This is fish number four, three, five, seven, this feature with a mock community members wanting to develop solutions using the custom executor.

Finally, we're also working up on wrapping key features and supportable launch of Windows shared winner beta on your comm I hope. This was helpful as a high-level introduction to our plans for told at six. If you have any questions about what time it's all God's sakes or really any questions about, get tapped on a pull-up feel free to drop me an email and de-spawn and get lab calm. Thank you until to you soon.