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

Need help knocking down issues #169

Open
markjbrown opened this issue Feb 4, 2025 · 6 comments
Open

Need help knocking down issues #169

markjbrown opened this issue Feb 4, 2025 · 6 comments

Comments

@markjbrown
Copy link
Collaborator

Hi folks. The issues list for this project is getting really long. Is there anybody that would be willing to take on any of these? There are some critical items that need immediate attention.

@bowencode, @crpietschmann, @hsavran, @codingbandit if any of you have cycles and can help, let me know. I'd like to setup some time to triage and prioritize. There is a backlog of PR's that are blocked because of #167. Also the .NET Fx for this thing badly needs to be updated. This would close a number of other Issues I see as well.

Let me know if anyone can help. I'll set up a bridge to discuss.

thanks.

@philnach
Copy link
Collaborator

philnach commented Feb 4, 2025

@markjbrown, I'd be more than happy to help in any way I can.

@bowencode
Copy link
Collaborator

@markjbrown I updated the .NET 8 branch I created a while back and started #172 from it. I haven't run any integration tests yet but will do that when I can.

@bowencode
Copy link
Collaborator

@markjbrown @philnach and I both checked #172 but it needs another approval so it can get merged. @crpietschmann

@markjbrown
Copy link
Collaborator Author

ok, got it. Looks good. Approved and hit the merge button on it.

I'm going to take a look and close some issues here that would be covered via this PR.

@stefanedwards
Copy link
Contributor

I recommend closing #154, #139, and potentially #152. Hope this helps.

@markjbrown
Copy link
Collaborator Author

@stefanedwards thanks. Been meaning to close some of these. I ran the GH actions on #152 looks good. I need to get @bowencode to review before merging as it touches parts of this code base he is most familiar with. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants