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

MSRV policy for libc crate is work in progress on the libs-team repo #2850

Closed
workingjubilee opened this issue Jul 22, 2022 · 2 comments
Closed

Comments

@workingjubilee
Copy link
Member

It's difficult to observe potentially important maintenance policy decisions if they happen in another repo. That said, I don't think it's inherently more or less proper to have the discussion in

to be clear. As has already been mentioned by one participant in that discussion, while this is clearly an important discussion for the libc crate, it may have ecosystem-wide impacts. Thus, treating it as a discussion for the libs team in general seems appropriate in other ways. Nonetheless, I raise it as an issue here anyways, if only to accomplish the feat of providing a redirect. It's a potential bug in the human interface of this crate, rather than the machine interface.

@workingjubilee workingjubilee added the C-bug Category: bug label Jul 22, 2022
@JohnTitor JohnTitor pinned this issue Jul 26, 2022
@JohnTitor JohnTitor changed the title Hard to notice maintenance policy decisions in another repo MSRV policy for libc crate is work in progress on the libs-team repo Jul 26, 2022
@JohnTitor
Copy link
Member

I've pinned this issue and retitled it for awareness, hope repo visitors find this.

@JohnTitor JohnTitor removed the C-bug Category: bug label Jul 26, 2022
@joshtriplett joshtriplett unpinned this issue May 15, 2023
@JohnTitor
Copy link
Member

Let's track this issue on #3248!

@JohnTitor JohnTitor closed this as not planned Won't fix, can't repro, duplicate, stale Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants