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

Release new version of @ethereumjs/client #1365

Closed
ryanio opened this issue Jul 19, 2021 · 2 comments
Closed

Release new version of @ethereumjs/client #1365

ryanio opened this issue Jul 19, 2021 · 2 comments

Comments

@ryanio
Copy link
Contributor

ryanio commented Jul 19, 2021

The last ethereumjs-client release was over a year ago, and since bringing it into the monorepo there has been extensive changes and improvements to the early development of the project.

This is a tracking issue to deprecate the old ethereumjs-client on npm and release the new one under the @ethereumjs namespace.

@holgerd77
Copy link
Member

Some additional context and thoughts here: I guess we are still pretty far away from a v1.0 release (one year plus) since there is various substantial functionality missing (tx pool, block production, tip of the chain behavior, reorgs, ...) which we just can't catch up within a few weeks or so. A real production client comes with certain expectations and even if we get the things from above working on a basic level, we are still somewhat far away from the functionality clients like Geth or Erigon are providing, their tx pool alone is highly sophisticated stuff and took weeks (months?) to implement. And we haven't even synced once to the tip of the chain of mainnet or a major test network. 😜

So I would really suggest to somewhat stay modest here. 🙂 I guess if we start with a v0.1 release and drop the pre-release state that would be already courageous. 😋

One thing also to consider strongly when planning on this: the Merge is "somewhat" around the corner and I guess it will lead to too much wasted ressources if we put too much energy into completing here on all fronts on a classic Eth 1.0 client when larger parts of this are thrown away along the respective integration. So we should in doubt rather focus on bringing things to work under merge conditions and then see after the merge how we position the client within this changed environment setting.

All this doesn't mean though that we can't pick up with regular client releases though and make our client a more public product. 😄

@holgerd77
Copy link
Member

My suggestion here:

We finish the following:

Then we bring the README up to date and also add a very explicit list what the client is and is not capable to do and then we release as v0.1 (following the last v0.0.6) release within the old ethereumjs-client namespace) and drop the pre-release to indicate that this is a new release quality respectively the client has taken a substantial leap on development and feature completeness.

@ryanio ryanio closed this as completed Oct 10, 2021
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