 Welcome to documentation office hours it's the 14th of April 2022. Thanks for being here. So today's agenda topics. I don't have anything on news but we could list news and then crowded enterprises my single big topic, and hope we could have Alex coaches through the process. Any other topics we need to put on the agenda for today. Okay, then let's go ahead. So I guess one item of news the, there's a proposal to delay LTS selection, LTS baseline selection and release by two weeks. It's being discussed in the developer list, or no in the UX sig list and mentioned in the developer list. Thanks in advance to you Alex for your, your help on getting us ready to do a good LTS for this, this upcoming LTS baseline. All right, crowd in enterprise. So I received email from them hang on I've got to show the email just to be sure that that I'm doing the right thing Alex so where is it. Yes, here it says okay, it says, thanks for asking for a free open source line license. I encourage you to create your translation project and upload files that should be localized. Let us know when it's approved created so we can approve your request. Okay Alex what do I do. I would start with clicking the link they sent you. Okay, good. So it's been like two years that I set up the instance for my project so I hope I remember everything correctly. Well, and, and I am confident you will, you will have forgotten more than I know, therefore we'll take will take your condition. Alright, so here we are. I should probably make it big enough to read. Can you read that. Actually, in fact, that is the regular crowd and instance that does not call the enterprise. Oh, okay, so and we need crowd in enterprise. Yeah, definitely. Okay, I mean we don't need it but that's basically what we have been talking about the past three or four weeks. Okay, so should I then just reply to them saying hey we want to use crowd in enterprise, because it's got the features we need for a project the size of Jenkins. Let me open it myself for you quick and current enterprise. Open source. Yeah, because basically on the current there's current enterprise and the regular crowd at the current enterprise is an entire own website, for example. So, yeah, be quite a different process. Yeah, if you don't mind I would share my screen real quick because I have just opened it in the meantime. Absolutely. Okay, so let's see yours. Okay, so this is this one. Yeah, because, yeah, because that is basically how you request an open source license for crowd and I don't think this is what they sent you. Actually, this, this is the form that I completed. And I definitely did complete this one. Next to is worried about item number four here. You do not have any commercial projects products related because cloud B cells and red hat and several others actually sell commercial products that use Jenkins, but they said no that was not a problem so this is definitely the page I submitted. Oh, okay. Yeah, maybe we are missing out step one here you have created a translation project and crowd. Oh, okay. All right, good. So what we need to do is create the project and then they'll promote us to enterprise. Maybe yeah, I think I quite don't remember the process but if they sent you the link and ask you to create a project. I was starting go ahead with that. Okay, all right well so then I'm going to switch back and steal back screen sharing and let's try this again. Okay, so here we are in create project. So Jenkins a project with the same name already exists. Okay. I mean I can call it Jenkins CI. I assume they are case case sensitive case insensitive they are okay so Jenkins CI public project now I don't know who has crowd in calm slash project slash Jenkins. It could actually be unclaimed or not public. Because I can't access it. Ah, right. Okay, good. All right. So, so but this one is a is a valid name for for the Jenkins project so Jenkins CI, then source languages English, if we say target languages. So, top 30. Yeah. And then I can remove some because there are a number of these that I'm confident we don't have any translation in them. I don't know about catalog. Okay, I'm going to guess not let them complain to me. See. It doesn't matter much whether we select them or not. This is just the initial setup. They might need to know who we are. All right. Okay, good. So then let's let's go ahead and not aware of anyone translating in Vietnamese. Okay, so just to create project. Yeah. Okay. Okay, your trial expires in 14 days. Add files for so so now what's my next step. Would you mind clicking on the settings tab please settings there right here. Okay. Yeah, and scroll a bit down a bit more. I'm actually looking for something that says that we are using current enterprise here all that they are. Oh, I see. Okay. Well, so shall we look for it. Okay, I don't see anything that says enterprise. Do you mind reopening the email for me very quick. Sure. Let's see the email was right here. Okay. A bit above. Please let us know when a project is created so we can approve your request so they basically need a project initially created. And then they can approve it and that then has the chance to grant us. Okay, so at this point, I just reply to them and say we've created it. Yeah, we have created this and would like to have Jenkins.com, for example, I will do that. Okay. I've created the project at there. Oops. And we would like to use crowd in enterprise for the Jenkins project. Okay. Anything else I need to say there. No, I don't think so. The future setup where we someday would like might might choose to have crowd in Jenkins.io. That's something that happens separately that doesn't really need their involvement that's something we change in settings later. Yeah, that is something they create. I mean basically they are sponsoring the license for us and hosting it for us. But we can basically create a CNAME record and point to something else under the Jenkins.io domain. Great. All right, so I've sent that. And we can ignore this. How did you hear about crowd in recommendation. Okay, good. Okay. Yeah, I just looked in my mails in the meantime, basically went through the same process. Okay, so you created your project and then they they approved it and promoted promoted it to use crowd in enterprise. Yeah, I sent them the link to the project on the regular cloud instance, and to me later. They sent me the crowd and enterprise URL back. Great. All right, well, so then that's that's very hopeful we may already get their response within a few minutes of of being here because at least yesterday they were very, very rapid in their responses. Yeah, I don't have the business hours but basically happened across three or two or three days for me so. Okay, even in May 2020. Oh, okay, all right. Waiting for crowd in. Good okay well so so we've made good progress then that's that's great so you okay if we take another topic while we're while while we're waiting for that. Yeah, for sure. Okay, so the Jenkins LTS 2.332.3 change log and upgrade guide. So, Alex has asked in Gitter. Any volunteers to create it mark volunteer the doc sig to create the upgrade guide, or to create a change log and upgrade guide. And as far as I can tell it looks like it's going to be pretty straightforward. Yeah, simple release this time. So, not a lot to write. There are two DRI issues I would like to back part. James opened PR a few hours ago for the CVE somebody filled. I think it was data binding or something. We upgraded. Yeah, Jackson data binding. I think it's going to be merged tomorrow so can like you back for the tomorrow or by next week release can get creation is scheduled for next week Wednesday so have plenty of time to set that up. And basil post that one issue on the mailing list I think something about NPEs in the locking handler for invalid configuration entries or something. If we have a positive feedback that the PR mergers actually addressing the issue I'm going ahead and backpotting this one as well and adding it to the overview of address issues. Great. And so, so this, this format is the perfect format for us because this is what we use to assemble the, the change log so thanks very much for doing that. I see that. Thank you very much also you remove the one or two entries this one, and I think there was one other and you've, you've removed them both because they weren't needed in the packaging right they were already there. Yeah, for some reason, I think it was a forgot, forget to remove the labels on the actual issues because they were included in the dot to release. I have a point here wouldn't make any sense anymore. Got it. Okay, and that may have been me that may miss that one so thank you that thanks for, for detecting that that's, I've got a checklist and sometimes I failed to follow the checklist for those those docs topics. Great. Thank you. Yeah, that's that lightly be the final list. A possible plus one or plus two issues adding apart. It's basically it. Excellent. Thank you very much. So I haven't actually reviewed the changes yet I still got to do that therefore you'll see I am not I've not yet done the check but I, I hope to do that today or tomorrow. And you're okay if this waits to merge until next week or do you are you feeling like you want to get it merged sooner. Yeah, I know. I wouldn't want to go ahead and and merchant until next week. Great. Okay, at least for the confirmation of basal's issue. If that is resolved and backboarded then and James PR isn't even merged yet so basically no rush here. Excellent. Okay. Thank you. All right, and then no, as far as I can tell there's no content. No content for the upgrade guide I didn't see any of those things that needed an upgrade guide and that's that's rather common for a dot three release so. So, thank you. All right. Any other topics. I haven't received a reply from crowd in yet so I fear we may run out of run out of of topics before we we get their response. We can do it next week if that's okay with you basal. Sorry, Alex. I think he's not here at the moment but yeah, I'm fine with that. Okay, great. That'll be recorded to shameful. Okay, great. Alex, thank you very much. If there's nothing else and I think let's call it done for today and we will check back in next week. If I'm if if I'm feeling pressed to get the crowd in work done much much sooner. I may ask you, Alex to have a session with me where we, we recorded separately and just do it sometime early next week depending on their availability. Yeah, let's see when they get back to us. All right. Thanks everybody.