Open edmorley opened 6 months ago
I think the answer is yes! I have in my TODO list to open the conversation to archive this repository, thanks for creating this issue @edmorley
Just checking in about the status of this?
If we're not yet ready to sunset the repo, could we at least merge the docs only #39?
In #39 we found that CI is completely broken at the moment.
I think this is another reason we should archive this repo now. (It can always be unarchived in the future if this project is resurrected.)
In #39 we found that CI is completely broken at the moment.
I think this is another reason we should archive this repo now. (It can always be unarchived in the future if this project is resurrected.)
@hone @jkutner do we have a process in place to archive repo under CNB?
My thoughts about this:
This integration is currently buggy/broken btw, and people are using it not realising it's not actively maintained: https://github.com/heroku/buildpacks-python/issues/196
The last commit to this repo was 3 years ago, and PRs aren't being reviewed (eg #39) - as such it seems this repo is unmaintained? Should it be archived to make the current status clearer?