This repository has been archived by the owner on Dec 7, 2023. It is now read-only.
node: Make 2.10.x long term support and shift to a maintenance only, use testnet resets for NEO3. #354
Labels
Comments
It looks great and precise, @canesin, I agree with the support and not accept new contracts after Q2/2020. Canesin, maybe this ROADMAP could also come in the README. |
erikzhang
added
the
discussion
Issue state: Proposed, to be discussed by the community.
label
May 10, 2019
I like this idea. I imagine it would make existing projects on NEO 2 happier since there is less stress to migrate until they are ready, and may avoid changes that may somehow break old contracts. |
Yes, i think exactly the same as you @EdgeDLT |
That was a great idea ^^ |
Stability is important |
@neo-project/core is there a consensus about this? |
shargon
changed the title
Make 2.10.x long term support and shift to a maintenance only, use testnet resets for NEO3.
node: Make 2.10.x long term support and shift to a maintenance only, use testnet resets for NEO3.
Dec 5, 2023
shargon
added
node
and removed
discussion
Issue state: Proposed, to be discussed by the community.
labels
Dec 5, 2023
Old, if remains, please re-open |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Following the neo-project/neo#727 line of thought in this issue is that while the proposed roadmap is great it is more work and limiting than we really need! All business need (like Nash) right now is a safe and stable NEO2 while NEO3 is not around, the desirable new fancy stuff can all go directly to NEO3. No need to so many backporting, that will only limit NEOs speed of development and limit how bold you can be, I know NEO wants to be bold ;) .
So with love from Vienna I hope that @erikzhang consider this and talk with Hongfei:
PS: That would also allow to release a NEO3 testnet this quarter already, that would probably speed dev and attract new people. 😉
The text was updated successfully, but these errors were encountered: