Skip to content
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

VVV PR status #648

Closed
topdown opened this issue May 16, 2015 · 4 comments
Closed

VVV PR status #648

topdown opened this issue May 16, 2015 · 4 comments
Assignees

Comments

@topdown
Copy link

topdown commented May 16, 2015

Is there a reason that some of the great PR's are not being merged in?
Especially a lot of the PRs from @cfoellmann
Like #611

Is there anything that can be done to speed up the process?

@cfoellmann
Copy link
Member

I think we need more people with commit access. That way we can establish a workflow with enough capacity to test and check PRs in a timely fashion.

@jeremyfelt
Copy link
Member

Only because I'm behind :)

I agree, I would like to mix up the current list of committers. Let me think through a few things that I'd like to establish first.

@jeremyfelt jeremyfelt self-assigned this Jun 7, 2015
@jeremyfelt jeremyfelt added this to the 1.3.0 (Next Release) milestone Jun 7, 2015
@jeremyfelt jeremyfelt removed this from the 1.3.0 milestone Feb 3, 2016
@jeremyfelt
Copy link
Member

I'm going to close this and focus on documenting the current processes in #962.

@lock
Copy link

lock bot commented Feb 23, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Feb 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants