Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Status: UNMAINTAINED #328

Open
tisba opened this issue Jun 4, 2023 · 4 comments
Open

Status: UNMAINTAINED #328

tisba opened this issue Jun 4, 2023 · 4 comments

Comments

@tisba
Copy link

tisba commented Jun 4, 2023

libv8 hasn't been touched in 3 years and it's not very likely it will be again.

It has since been replaced https://github.com/rubyjs/libv8-node. It has binary distributions for more architectures and most importantly more modern versions of V8 (afaik up 11.3.244.8 in the current release).

I propose to archive this repository, pin either this issue (or another one explaining) and also add info to the readme.

-cc @SamSaffron

@SamSaffron
Copy link
Contributor

yeah I think this is the right thing to do... I think you have rights? go ahead and do so.

@tisba
Copy link
Author

tisba commented Jun 5, 2023

No I don't have permission to archive or pin issues.

But I'm happy to prepare an issue and a PR for the README changes.

@lloeki
Copy link
Contributor

lloeki commented Dec 4, 2023

I have gone through all issues here, just too make sure no thread was left hanging.

With the last bit of this done I'll push an update to the README and pin this issue.

I believe the same should be done for therubyracer, which already has an issue that I just pinned, and a small note that I think should be a bit more prominent.

@lloeki
Copy link
Contributor

lloeki commented Dec 4, 2023

Done in f7f0b56

@lloeki lloeki pinned this issue Dec 4, 2023
@lloeki lloeki changed the title Archive this repository and point to libv8-node? Status: UNMAINTAINED Dec 4, 2023
lloeki added a commit that referenced this issue Dec 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants