Han-Wen Nienhuys <hanw...@gmail.com> writes: > On Fri, Jan 24, 2020 at 11:58 AM David Kastrup <d...@gnu.org> wrote: >> >> I guess I am a developer with repository access, but in Salzburg, >> >> Werner >> >> offered to me to do the mechanics of shepherding the patches through, >> >> and >> >> I'd like to take that offer. My time is probably better spent >> >> navigating >> >> the arcana of the GUILE 2 / 3 transition. >> >> >> > >> > OK, that looks reasonable. That means patches will *not* get pushed >> > "without any of your involvement" but you have to ask someone, i.e. >> > Werner to do so. Probably he's monitoring this anyway, but you might >> > ping him again privately, just in case. >> >> I can also do this. The decision should still be done individually: >> some patches reach "push" in spite of comments on Rietveld, and James >> implements more of a janitorial process and the decision which comments >> may be showstoppers really rests with the patch submitter. > > Thanks, that's greatly appreciated. > > BTW, Do issues get closed on Rietveld automatically too? I still have > many open reviews from many years ago.
The only person able to close them is the author. Not sure whether a project manager could, but then this would be quite a bit of additional work. I probably have accumulated a lot of them by now, too. Probably a few years since I last remembered to clean up. -- David Kastrup