 Welcome everybody, so the weekly Evergreen open planning meeting. This week we are going to make as usual for people new coming here, basically doing a status call about the Evergreen, 10 kids Evergreen initiative status. So right away I'm going to give the stage to Adrien because Adrien is a new member of the team at least for a few some time and Adrien is currently exploring, by the way he already started working on this, about what it would take to actually make Evergreen work on JDK 11 so it would both I guess respect the tagline of Evergreen or having a lot of things already up to date, you know a very short feedback loop and at the same time it's likely to be something very interesting to also provide some interesting feedback with regard to the whole JDK 11 upgrade work so yeah Adrien can you update us a bit on where you are and about that task. Yeah so at the moment I'm looking at the code what create the current flavors and how I can create a new one adding a new using the process to include Java 11, it's really early stages so I have nothing really to show or to say about it quite yet but Yeah it was started this morning for people watching so yeah. Yeah exactly so it's still early stage for me but I'm pretty sure that you have something relevant for the next meeting. Great and so just for people watching and for Mandy who knows more about that in general that the path we are following right now is to introduce a specific flavor for this because then you know we'll be able to for instance have specific plugins for that flavor specific JDK because you know it's a specific Docker image and many things like these that would actually allow us to deploy even up to production without you know having some kind of specific backend or whatever to run this so that's that's going to be interesting I think. So and so I don't have anything in progress because this morning I actually closed a lot of things and actually implemented a very low small one which is so Amanda if you have a look at the code you'll see that I renamed the environments into flavors directories so that it's slightly less you know lowering what the fuck per line ratio basically because there was places where we would call things environments where we actually you know were calling it flavors you know by voice or while explaining that to people so I felt it was the right time and and yeah very important to do it right now as Adrienne and possibly others are going to have a look at those things and start wondering what the hell those things mean so that's it and I hope to be able to get back to more things in the next coming time but not sure in that at least the next few days that's for sure I think those things we're already here for since quite long so there's nothing I guess apart from this nothing much to say about that too far today at least maybe just a later later upgrade there was so the only thing about evergreen in general so the talk I gave in Copenhagen code com was recorded and published recently so I think it's around here let me see and more I thought it was published here so anyway I will probably post that somewhere we probably should put that in the repo in the git repo links to presentations about the vagrin I think it would make sense indeed that makes me think right now so I know the video has been recorded and published but possibly not yet publicly because you've been reviewed I received a mail recently from track map basically so let's take that aside so I think that's fine and I guess we can probably move to closed closing anything else Adrienne or Mandy no I just saw something about the environment to flavor renaming and I will update the ticket because I think we forgot something right about that maybe if you're talking about for instance the essential that jamal that's normal to keep that environment because this is so this is something I actually talk about I thought about yeah so let me see environments if I find it right okay right that's the one so yeah there's a place where basically you know in our and in a central document so what I'm talking about is that and so that I consider renaming but I don't think it's it's a good thing at least to remain to rename it right now because it's not a format only used in it's a more standardized format I would say if not if even if right now there's no real programmatic check or right there but yeah this is coming from the JEP 309 I think just a bit of material so basically this thing is used so by evergreen but it's also used by the custom warpackager that tool that creates that is able to create given that kind of file a specific you know prepackage instance of a war with included plugins and everything that's already used for instance in the Jenkins FireRunner tool and many things like these so you see here it's used in many many places right now and so it's also used I think for the testing in a PCT and essentials test that's been written by Rao already some months ago and many things like this so that's why we can really rename it like this but yeah maybe I don't know if it would make sense to consider renaming it upstream I tend to guess not well but yeah I understand where what were your where your question was coming from and I'm pretty sure actually our parser would need an update or some improvement because it's basically removing comments so that's why I didn't bother I'll try to add a comment there because I knew it would be removed by the make Generate Essentials targets so yeah that's a waste anyway anything else nope I did it thanks yes that's that's one of the things that probably not really are kind of ambiguous from the ground up so yeah sorry about that anything else Mandy nothing new for me cool thank you so everybody thanks for watching and see you next time bye