-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project Velocity #1530
Comments
If you want to pitch in, I think you can begin by simply starting to help to review PRs in the backlog. W.r.t the number of open prs, it's typical for open source projects that some contributions may just never be merged/accepted. |
Will do. I've got a few code reviews out now (and know @torkelrogstad has been extremely helpful in reviewing some of mine, e.g. #1503) My point on the stale contributions is that generally 3/4-year-old stuff with a bunch of merge conflicts should generally be closed and the PR's that are opened/reviewed (e.g. #1467 which fixes #1466 and #1519) should probably be merged. The longer these things stay open, the more merge conflicts occur and the slower the subsequent release cycles. I will definitely start reviewing some more of these PR's though |
I just merged #1537 and and going to make some attempt to both triage issues/PRs and do some reviewing and merging where possible. This was discussed with @Rjected and @someone235 on irc. |
@jcvernaleo I saw this conversation, but missed you guys buy a few hours. I'm generally on irc as |
Also @jcvernaleo happy to go through and triage if we can tag (no permissions right now) - Went through about 20 pr's and approved/requested changes as per @Roasbeef a few weeks ago, but that's all we can do. Those 20 represent almost all of the non-stale commits |
Since we have a plan for triaging PRs/issues, getting some more folks to have triage permissions, and dealing with the PR backlog, think we can close this issue? |
Yep. |
Yeah, I meant to reproduce some of that chat here but got distracted tagging things :) |
@jcvernaleo @jakesyl Please count me in on this. I don't have triage permissions, but tried reviewing/reviving some stale PRs/issues here: https://github.com/btcsuite/btcutil If it helps, we can start a GitHub Project board to make sure open PRs are not lost forever and have a clear path towards being merged (at least the ones that are ready). What do you think? |
@onyb no objection to a github project board although I have no great idea how to best structure it myself. If you have clear ideas, might be easiest to open an issue for it telling me what you'd need me to do. I do plan on getting back to some of the open PRs soon. I guess not too surprisingly, a global plague has left me with less time and focus than usual, but trying to get back into a kind of place (for work and projects anyway). |
@onyb I think we've got a pretty clear path around the ones that are ready. As I've mentioned, I'm pretty busy the next week and a half or so but after that I've got a few PRs that I'm going to put some finishing touches on and merge |
So I want to prefix this with saying the entire community is extremely thankful for @Roasbeef stepping up as a co-maintainer and leading this after the decred teams activity decreased and they focused on their altcoin. Your contributions here/leadership on lnd are awesome (and I'm not kidding, there's literally a reddit thread refusing to believe your one person)
With that being said, we've got a pretty substantial backlog of pull requests 100+, a lot of which are approved for review than going stale or just not getting merged after a few months. Would it make sense to add more maintainers or figure out a peer review/ci workflow where you don't have to personally merge in every PR?
Just trying to figure out if we can do anything to get some of these PR's in more quickly or think about a more long running fork
The text was updated successfully, but these errors were encountered: