Hello, my name is Rick tonight I'm the product manager of the configure group- and this is the 13.2 release kickoff. For our group, we are responsible for command disintegration, terraform integration, all two DevOps server, last chat ups and run books, and our primary focus is on tremendous management, terraform and outer devops in the coming release. We are focusing on four goals: first, is to move forward with our cloud native bait, back support under outer DevOps and actually are starting to deprecate Heroku support.

Second, we would like to ship the first alpha version of the lead lap, tremendous agent.

We are pretty determined ship it at least four gitlab contributors, including community contributors, but as a stretch goal we hope to be able to ship it for broader audience as well and the third goal we are pushing forward without reform improvements, we've started to add in the past month and we are improving the guitar from stage to be collection, ready and we are running the next iteration of the transform change widget that we shipped last month. But let's see these issues in detail, you can see from our planning issue which one are deliverable.

Those these are the moving out to DevOps to Humphrey, actually suggest an expiratory issue as a result is not in our directions. It's it's in order for us to be sure that in the next milestone, we can move out to DevOps to hand three in the turf from land we have here. The adding supports for tough. For me most a data source and we are trying to add environment, supports inter formation back-end that we use under the hood, and this will actually simplify tram usage. A lot.

The setup of our current term get Lamanna state a lot on the cabarrus agent side. We are very close to ship the proof of concept and we would like to ship the agent inside GD k, GD GD k as well, and the deliver of all we have to Mort are formulated deliverables, one is to limit the artifact that we store with reform plan. This is both the security issue on comm, but actually this can prevent wrong files to be stored, strap implanted the intubation wouldn't work anyway, and the other is to improve.

The error message is individual. Besides this, we have several stretch goals. Some of those are related to beta packs, the cognitive base back change. We are pushing forward and some are related to the HR phone provider. Others are related to UX depth issues and on the design side, we are actually trying to move our our form maturity level to viable, and for this we are preparing a new XCore card analyzes and otherwise we are working on designs to add even more support both to terraform and both the cube and this agent setup part.

This was the release kickoff for the configure group in 13. The thank you for your attention.