 Recording is starting. Welcome. This is the 14th of September at 2022 Git Cash Maintenance Project. So Hrushakash, I have merged the changes into the Git Plant plugin and hope to release it within the next 24 hours. So congratulations. I'm not as confident on the changes in the Git plugin because I want to do some more testing. I want to be sure that we get the help in etc. So there are more things to be done there but I wanted to get the Git client plugin out there because that way we've got a stable base for it and I've got a way to deliver jgit5.15.1. So thank you very much and we'll continue the work with the Git client or with the Git plugin in the future. So thank you very much. So that's some good news because the code has been merged. I had it out regarding the Git plugin. Now how are we going to test it? Are you going to run it on your machine to check? Is it executing as expected or? Yes. I had it out. Okay. So before I'll do further testing, there are some things that I've got to be sure. For instance, we didn't get the online help in yet and I'd like to have online help available before we merge. We've got to be sure we get documentation in and if you're available to help with documentation, great. But I think your first priority has to be update your project page on Jenkins.io and if you're not feeling well, that may be all you do is update that project page so that you can get it it completed to satisfy the requirements of Google Summer of Code. Okay. So now in terms of I'm hoping that you're interested in continuing, but you certainly aren't required to continue to work with me on it. But one way or the other, what you've done is going to be merged and we will arrive at shipping it. I'm not sure when yet because I've got some travel that I have to do later this month and preparing for it that makes it difficult for me to say when I'm going to do anything else. But I'm looking forward to it merged and shipped and delivered and touted. Oh, we can keep working on this thing. If you put any comment on that pull request as well, I would see an update and do any changes required from my side as well. So great. Thank you. Thanks very much. Now, I assume that school is starting or has started? Actually, we had college the entire summer, like for a summer is yeah. Okay, so you were already in school. This is no different. Yeah, yeah. So kind of used to it. But I can, yeah, you know, I keep contributing. That is what from my side, you know, try and finish it and deliver it as expected without any issues in a very safe state. Excellent. That's wonderful. Thanks very, very much. Oh, and this I updated the Git client API, you know, to return a Boolean and that I have updated exchanges in the Git plugin as well. So now I know if the Git maintenance is being executed or not before I was insured. But now in the plugin, we can confirm that the maintenance has been executed or not. Also, the cash size, now I'm displaying it only in terms of MB, like as we have discussed. Okay, so that has become easier to sort as well. Okay. Now, I couldn't, I thought I'll work on, you know, skipping the caches for repositories less than 100 kb, something like that. But then I, you know, because of this thing, I couldn't work on it. Right. No, no problem. I'll try and complete it by this weekend. That's not an issue. Also, there are, I've updated the help files, like added the text from my side, but it isn't still working in the UI. Two, three maintenance tasks help file have updated. So that also I'll finish and push it by this weekend so that, you know, it would be completed. Other than that, I think, you know, everything looks that goes screened as expected. Wonderful. Prushakash, thank you very much. Congratulations on your accomplishment and thank you. I look forward to those last little bits and we'll keep working it. Yeah. Thank you. Thank you very much. So in terms of updating the project page, are you comfortable with the kinds of things you're going to insert there so that you've got a good, so that it's clear to the Google Summer of Code people just how, what great work you've done, et cetera. You're comfortable, what you'll embed there, et cetera. I was thinking of adding, so basically first there's a project abstract, what is a project you're going to talk about. And then I was thinking about, you know, the deliverables, what exactly was required by me. And then one architecture diagram. And then what I've done in the first phase. And then it's video, the YouTube video. And then the second phase, what I've worked on. And now, you know, attach links to the Git Client plugin, the Git plugin. That's what I was thinking. I like that, that link to the, link to the poll requests. And now, now that we've got, if we're lucky, so, and this is me saying if we're lucky, but if things work out the way I hope, you may be able to link to the Git Client plugins release note, or the changelog for 3.12.0, because it now lists the automatic Git Cash Maintenance API or it will when it's released. I can see it as a pre-release. And when I release it, and if we finish early today, I may be able to release it immediately after this meeting. Okay. So I can attach that as, but where do I find the link? It would be in the read me or something. Yeah. So here, I'll help it if I'll just paste it to you and show you what, how it will look. Okay. So it would be like this and two good. All right. Yeah. So I'm going to paste it into this, into the zoom meeting chat channel. That is the previous is the, let's see, is the changelog for the previous release. So it's just an example. And then this will be the link for the new release after it has released. So it's broken link right now. So don't be dismayed when this second thing is not resolvable right now, because that I can, or even I don't see it. What I see is a pre-release of that in my, in the queue showing the correct things. So it will be at that location once it is released. This thing would happen on its own? Or do you have? No, no, I know. It should happen on its own. That's a very good question, actually, because in the Jenkins project uses continuous delivery for many plugins. However, I am behind schedule and the get client plugin doesn't use continuous delivery yet. So in a perfect world, the merge of your changes would have automatically run the release process and automatically published everything. And for a number of plugins, for several other plugins I maintain, that's exactly what happens. But the get client plugin, I'm still hesitant about it, right? Because it's got a lot of users. And if I make a mistake, it hurts a lot of people. So now if I go and download the Jenkins long-term software, and then if I download the get client plugin, my code will be in it, right? Once you release it. Right. Once it's released, absolutely. Then, so for instance, 24 hours from now, you should be able to, when you start Jenkins, you'll see a get client plugin version 3.12.0 that will include your code and jget 5.13.1. Yes. Okay. Yeah. That's something to be proud about. It is. Well done. Yeah. So are there any other topics that you wanted to be sure we discussed today? I think that's a mark. There's nothing else from my side. The final thing is that I'll put a sender message in the GitHub channel. Okay. Good. And have you responded? I think, actually, I think I know the answer. I believe I saw that you had responded to the Doodle poll trying to find a time for the presentations. Yeah. Yeah. I have responded. Yeah. Very good. All right. Excellent. Well then, Ruchakesh, thanks very much. Hope you're feeling better soon. And congratulations on a great project. Thank you. Thank you so much, Man. It was very nice working with you. Real pleasure with you as well. Bye for now.