 It's the second of August, 2021, or if you're India Standard Time, it's the third of August, 2021. Welcome. Let's look at our agenda. Okay, so you should see notes. I've got 2.305 weekly change log, change like automation 2.301 302.1 LTS change log upcoming events that JDK 11 Docker transition, and then Hacktoberfest and we're now next week. Okay, oh, and I have not started that yet. So get it done. Okay. So any other topics do you rush that you need to add or others. So I had this topic for 2.305. It's already there. So I would love to add on that. Great. Okay. Right. Right. And then this one will probably be me. Okay. All right. Excuse me, pardon me. Okay. And I think, in terms of, well, yeah, so let's let's take the weekly change log first. Do we, do you have a question there or do we want to just review the poll request together. I have a question there. So I was working on it this morning and I was not able to generate it with the help of the Docker. Okay. Generation failed and what was the failure message. It says invalid byte sequencing us as guy argument error. Okay, so what that means is that means someone inserted extended characters into the data. And that's valid but it means we've got to change the locale to run the tool in a specific locale. In locale that understands a wider range of characters. And so I think what we ought to do here is let's do an experiment. We'll do it together trying to I think what we do is we set Lang equals C dot UTF eight. And then run the tool. So let's let's try it and see if we can make it go. Is that all right. Okay, so first things first. I need to check out the master branch, and it is current. Okay, that's good. I've had a system crash. This week so I'm, I'm having to reestablish my system so now I've got to work it out where my tools are, and I need to clone them again so it'll be just a moment. Oh, and maybe it won't be more than a moment my like extra copy is gone. Okay, so the computer didn't restart yet. So I'll just read the directions and follow the directions just a minute. Oops, that is right here. So what I need is the GitHub repository for Jenkins.io. And there is a contributing file. Oh, no, no, no, it's in the change log content data change logs style guide. Now is this where the tool is described. No. Okay, just a minute. I'm gonna have to go do some searching. Okay, so it's change log generator. So let's go find that there. Okay, so the change. Ah, yes, that's it. So we're change log generator. That's the one we need. So what it tells me is. Oh, that's right. And I am going to need an auth token so dirage I have to stop sharing my screen briefly while I generate a new authentication token so I'll stop the share. And go to my GitHub account. Sorry, this, this would have been much easier if my computer hadn't crashed last week. Okay, so settings. Developer settings and I need a personal access token, which has I need my two factor authentication device. Really come on. Okay, there we go. Now, change the lock to make it good for 90 days. Okay, there we go. So just to confirm my screen is not shared right. That's right. Okay, now this. Alright back to sharing again. Sorry for the delay there. That needs to download the image. And now it will do that and then it should fail immediately because I'm in the wrong directory, but I've at least got the image. So now in the Jenkins directory, and this should fail with instructions are do this. No tags could not read. That's really strange, dear. Sorry for the painful process here, dear. You just a moment. You should give us all the tags which it does. Okay, there we go. Now this I would expect to fail with a complaint about. There we go. Okay. So I think this is what you're seeing invalid byte sequence in US ASCII. Right. Okay, so now what we need to do is we need to report what are the available locales. There it is. We'll just let's try this one. So in addition to the minus E GitHub off equals that we say minus E Lang equals. See that UTF eight. So that says please process things. Well there goes that token recorded for life. So I'll have to throw that token away after this session. All right, so let's see the trick was Docker. Okay, so here we go and we're going to say minus E Lang equals C dot UTF dash eight. And let's try it again. Okay, good. So that's better. Okay, so the technique was, and we should probably put this into the change log generator repository so let's do that with a pull request. Yeah, check out minus B. Add Lang to awkward command line. Okay, so this one C dot UTF dash eight right C dot UTF dash. Yes. Okay. There it is. All right. There we go. Use a UTF eight locale to process more characters. Okay, so that that's been submitted that won't block us. So how about if we switch from me sharing my screen to you sharing yours and we'll have you run the same command. And then we'll that way we'll be confident that that we've got it and I'm going to go delete my token that I just shared publicly. All right, good. So the recording of that token doesn't matter now because it's no longer valid and get up. So I'm assuming you're able to see my screen. I am. Yes. So it looks like it started. That's good. So did it work. Or it is working. Excellent. Okay, very good. So, great. So, I think I'll take, take it over from here. Okay. Great. Well, thank you very much for doing it. Sorry, you bumped into this challenge. Actually, while we're here. Let's have you for give a review of that pull request that I just submitted. So I'm going to paste the pull request ID into our chat window in. And now if you could open this in your web browser. Okay. Yes. Let's review it and give your approval. So, what you do is in the top right hand, or the, there's files changed a lot. So below that. So click that. Okay. And then what it will show you is the differences. And then, and you see minus E lang C dash. UTF dash eight of the three changes we made the top right hand corner has a green button review changes. Don't write it. Yes. Click. Click the approve checkbox. And usually I like to put a comment up there's something in this case probably something reviewed during Docs office hours. Yeah, that that's good enough and then click submit the submit review button. So what you just did is you've said, I have reviewed this change and since you've used it and confirmed it works. I feel pretty good that we can say yes, it's been reviewed. What we have to do is find somebody else who can actually merge that. Right. So, anyone can review PRs. I thought you need to have some privileges. No, no, in fact, it's quite valuable you can review PRs what you cannot do is you can't merge them. And so, so you, you have permission to give comments and say hey, this looks good to me and, and you see over on the right hand side your name is there with a checkbox that says having it has reviewed it. And it's quite valuable to have people who review things because it's, it takes us a lot of time to do reviews. So having one more reviewers is a reviewer is a big win. Really great. Okay, so we've got, we've got that set. So let's, let's switch, I guess we should probably switch back to our agenda and I'll see if there are other topics to bring. Okay, so I'm going to switch and share my screen. Okay, so. Whoops. We should make a note here CPR. Where did I put the poor. Excuse me, dear. Sorry. Ah, here we go. This one PR 15. All right, good. Anything else on the 2.305 change log I assume that you'll work through it and after you're done with it will get it reviewed and merged. Definitely yes. Thanks. Okay. Change log automation. I'm sorry I have mark has not yet reviewed the reviewed the PR. Daniel Beck expressed his thanks that others are willing to be involved. Review and revise. So that was a good sign. I think we've overcome his concern that change log automation would cause their the change log to be worse, not better. And I assume. Are you still willing to be a reviewer and part of it I assume you are dirage. Yes. Excellent. Thank you very good. Okay. The next piece is the 2.302.1 LTS change log, and the back ports have no back ports have been proposed yet. And an error was detected in the definition of the branch. That is a good story to show. I'm going to show you what what it looks like now and why we'll have to fix it. So is the text on the screen big enough now to read. Yes. Okay, good. So let's go to the Jenkins repository and I've got a command that I use called get log dash a get alias and we can see. aliases. No, there's this command I use that helps me visualize it's get log minus minus graph minus pretty close one line a brief commit decorate. And I use that. And what that shows us is, okay, here is the master branch, the red is remote branches the green is local branches. This is the Shaw one and the, the graph thing here the edges of the graph are showing which things are parents and which are children. What we see here is if we look, you see here's the tag Jenkins dash 2.304. Alright, Jenkins dash 2.302 or 303 to that 302. But as we continue backwards. I think we will find. No, let's see stable dash 2.302. Okay. Here we go we'll look at it this way. So 2.3 stable 2.302 is this upstream branch. So here's the upstream branch but if we look at this history. There is something going on here. That's caused it to be based on the wrong location. So, here is Jenkins the tech for Jenkins 2.299. The stable 302 should be based on 302, not on something prior to 2.299. So Daniels detected and and I agree with him, the branches defined incorrectly. So we need to fix that and define the branch correctly so that it's based on a on the on the correct version of Jenkins 2.302 which is right here. So that's something you or I can do but that's something that the release, the release lead will need to do. And so I'm not going to attempt to generate the change log until that's done. We could look we can certainly look at the things that have changed in the in the actual change logs themselves but, oh hey that's great. I have permission to merge this. Okay, and you've approved it so I'm going to go ahead and merge it. Done and delete the branch. So back to our change log generator so we've got to do. We need to be based on the correct branch branch point before we write the change log. So like, how did this happen like automatically or just by mistake. Human error. Yeah, the release lead just made a mistake in defining the branch. And it's happened before so it's not a shock usually the way the way the branch should be defined I believe is by looking for the Jenkins dash 2.302 tag, and then going one commit after it. And that would be the place where you would put the put the branch point base it off of that. So we said, check out minus be stable dash 2.302 track upstream slash stable dash 2.302. Okay, and then get reset minus minus hard and point it here now it will tell us just how different they are. And then it will tell us says there are 54 branches on one layer or 54 commits on one leg and 13 different commits on another. They are clearly it's the branches clearly not where it should be. Right. Okay. So, alright so we'll hold hold the change log generation until next week or later. How much time will it take for me to get a view on. You know, you know all the commands and you are running it like it's English for you. So, any tips on that. On using get that kind of thing. Yeah, because you use it like your, it's like plain English for you. So you do it really quickly and you do it. Yeah, well, and, and that's, that's more, that's more a result of lots of damage from having spent a long time doing get commands so you should you should not not that's neither is that a goal, nor particularly helpful for you. If you find it helpful that's great but for most people, they just learn and correctly use a small set of get commands and that's more than good enough. Makes sense. So, if now if, if, if you take a job as a release engineer or as a branch master or something like that. You'll, you'll, you'll develop it just because there's no avoiding it. All right, good so we've got, we've got that part, the LTS change log is is on hold. So the job, the JDK 11 Docker transition mark needs to finish the job. Finish the Jenkins, the Jenkins enhancement proposal. The model needs a number of a number of hours of writing several more hours before it's ready to submit. But the, let's see, the coding is in progress for to improve Docker image generation. So that tomorrow's for today's the next weekly is scheduled to deliver a multi architecture Docker image, which means if we're lucky it will run on AMD 64, the current arm 64 power PC 64. And system 390 X. And that's from a single image. Really excited about that one because that gives us flexibility with which computing platform we use in particular arm 64 is a lower cost computing platform on a number of the cloud providers. Oh, I didn't know that we had some restrictions to hardware. Yeah, the the Docker images only today only run on AMD 64. And so this is this is giving us this if it's successful tomorrow will give us additional images or additional facilities inside the existing images and so a user will log into their arm computer and just type the command Docker run. Jenkins Jenkins colon latest, and it will run run on arm. Whereas today it just fails. Well, then this will be really helpful. We hope so. Yeah, I, it's been on a roadmap for quite a while, and it's really exciting that Tim Jack home and Damian do portal have made such great progress on it. They've made the build process from two to five times faster. The build and test process is two to five times faster. And they've added these additional capabilities. Wow, that's amazing. Oh, any questions on the Java 11 transition. No, nothing from my side. All right, so let's, let's talk about the one that should probably spend most of our time and this is Hacktoberfest. So I have not yet reviewed the materials from last year to get started maybe we can you and I can start that right now Jenkins Hacktoberfest and see if we can find it. Hacktoberfest and Jenkins the FAQ. Okay. All right, there's one. And then the Jenkins event kit. And because we'll probably be remote here I don't know that now then we've got Hacktoberfest 2019 blog. We've got 2017 and somehow I'll bet there's a 2018 blog as well and if I just look for the keyword Hacktoberfest Jenkins. There it is 2018. And it looks like we may not have either we didn't blog about it in 2020 or we did not have a the tag applied. Okay, so here we've got Beijing niece Jenkins online meetups. 1819. There we go. It's in the new year report. Okay. Event kit. Oh, and we need Hacktoberfest. My mistake of course, is that in events. Yes, that is okay. Oh, right, right, right. We're out event and where are our events here they are events. And that's a little frustrating no link to this. Here we go. Okay. Hacktoberfest. Okay, so this tells people how to get started talks about the Jira issues featured projects which we need to get featured projects that's good. Issues. Hey, that's not a bad collection. Do you watch, look at that. We've got 14 open good first issues now in the past we've like to have 30 to 50, but just having 14 is already pretty good. On the Jenkins core we've got 54. That's good. So this plugin site may have. Yes, it has to. Okay, good. All right, so we've got and Jenkins file runner has some tecton client plugin has a pair. Very good. Okay, so this is looking promising. We don't have. Yeah. Okay, no, no good first issues there. Okay. Let's see if we can find the hacktoberfest retrospective from last year. Not seeing it. Okay, oh, hey, there's a nice blog post from Andrea Musap. Okay. Good. All right, so, and I'll have to go looking for to find the hacktoberfest retrospective. I don't see it immediately. Dear, I apologize that I'm not as organized for the hacktoberfest conversation as I should be any insights you'd like to offer or suggestions there on how we approach this our next our next meeting of advocacy and outreach I believe is in two weeks. That right. Yeah, so it's it's the 12th and that that may be good enough for our next conversation. So let me get started on on a community Jenkins that I location and on a document to talk about how we'll do this. I assume you're willing to you're willing to collaborate with me on that document as we try to try to describe how we approach it. Great. All right, excellent. Thank you. That's, that's all that I had for today. Any other topics you wanted to bring. No, nothing from my side. All right. Have a great day dear Raj. Thanks very much. You too. Bye bye.