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

Anymap isn't unmaintained anymore. #1378

Closed
wants to merge 2 commits into from
Closed

Conversation

MisileLab
Copy link

Anymap released version through chris-morgan/anymap@2e9a570

@pinkforest
Copy link
Contributor

pinkforest commented Aug 22, 2022

@chris-morgan is the maintainer I believe - status update should come from the maintainer some way ..

Repo activity alone doesn't matter much -

I don't see any comments re: maintenance in the Issues or any explicit publication re: maintenance status

Also the crate has not been updated for over five years - as these are what we track
https://crates.io/crates/anymap

Also was the withdrawal happen despite the above, we would use the withdrawn = "YYYY-MM-DD" field for this

@MisileLab
Copy link
Author

@chris-morgan is the maintainer I believe - status update should come from the maintainer some way ..

Repo activity alone doesn't matter much -

I don't see any comments re: maintenance in the Issues or any explicit publication re: maintenance status

Also the crate has not been updated for over five years - as these are what we track crates.io/crates/anymap

Also was the withdrawal happen despite the above, we would use the withdrawn = "YYYY-MM-DD" field for this

crate prerelease updated

@MisileLab
Copy link
Author

I will add withdrawn section

@pinkforest
Copy link
Contributor

pinkforest commented Aug 22, 2022

Thanks for pointing to the prerelease from six months ago -

We dealt with this crate 18 July: #1281 and it led to this: chris-morgan/anymap#45 where the maintainer hasn't reacted yet.

EDIT: Seems like last word from maintainer was:
"almost all issues have been resolved": chris-morgan/anymap#37 (comment) - back in January

Has the maintainer fixed the soundness issue(s) that I believe led to people wondering about it's maintenance status ?

e.g. have these soundness issue(s) ended up into the release and will these end up into the potential future 1.0 release ?

@erickt did this originally: #906

This was the original soundness issue I believe: chris-morgan/anymap#32

@elichai @hellow554 were working on this: chris-morgan/anymap#32 (comment)

I wonder if the maintainer intends to keep maintaining it or was this just one-off pre-release six months ago that hasn't eventuated to a real release .. yet perhaps ? Would like to hear from the maintainer re: intent / preferences.

Have we raised the ticket in the repo to ask about what the maintainer's preference would be re: maintenance status ?

I mean we know the maintainer is now doing something obviously but the maintainer might want us to keep this status 🤷‍♀️

if the maintainer prefers to leave it as unmaintained status then we can instead adjust the soundness advice as fixed in 1.0 release - if the fix has been published - but leave the unmaintained as-is.

If the maintainer both prefers to have unmaintained status withdrawn and the issues are fixed (and published) then we can mark the whole advisory as withdrawn ideally.

@pinkforest pinkforest added Feedback Needs more feedback Propose-Close Propose-Close and removed Propose-Close Propose-Close labels Aug 22, 2022
@MisileLab
Copy link
Author

I think maintainer one-time patch, not maintained. hmm, May i close pull request?

@pinkforest
Copy link
Contributor

Can we try e-mailing the maintainer ? fix would be always good

@pinkforest
Copy link
Contributor

And yeah I think Closed until we hear from the maintainer. Thanks for the effort though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feedback Needs more feedback Propose-Close Propose-Close
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants