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

Neo v3.8.0 #2974

Open
roman-khimov opened this issue Nov 16, 2023 · 9 comments
Open

Neo v3.8.0 #2974

roman-khimov opened this issue Nov 16, 2023 · 9 comments
Labels
discussion Initial issue state - proposed but not yet accepted milestone

Comments

@roman-khimov
Copy link
Contributor

Discussing v3.8.0 milestone here.

I think that's where we should fix #1526 and that should be the main thing for this release.

Other issues moved from #2095:

It should be set ~2 months away from 3.7.0.

@roman-khimov roman-khimov added the discussion Initial issue state - proposed but not yet accepted label Nov 16, 2023
@Jim8y Jim8y pinned this issue Nov 29, 2023
@AnnaShaleva
Copy link
Member

@roman-khimov, we may want to include #3210 into this version.

@roman-khimov
Copy link
Contributor Author

I expect modules to be merged into monorepo in this cycle, so the list can be managed in https://github.com/neo-project/neo/milestone/3 after that. This issue is for release-related discussions.

@cschuchardt88
Copy link
Member

I expect modules to be merged into monorepo in this cycle, so the list can be managed in https://github.com/neo-project/neo/milestone/3 after that. This issue is for release-related discussions.

I can do that

@vncoelho
Copy link
Member

vncoelho commented May 10, 2024

I expect modules to be merged into monorepo in this cycle, so the list can be managed in https://github.com/neo-project/neo/milestone/3 after that. This issue is for release-related discussions.

This is a must to me, milestone 1. Our team needs this to come back with dBFT Unit Tests.

@vncoelho
Copy link
Member

I expect modules to be merged into monorepo in this cycle, so the list can be managed in https://github.com/neo-project/neo/milestone/3 after that. This issue is for release-related discussions.

I can do that

Please proceed with this honor @cschuchardt88 .
However, please avoid ANY unnecessary change, just do what is needed for the migration.

@roman-khimov
Copy link
Contributor Author

We need a name for D hardfork, btw. This won't be easy.

@shargon
Copy link
Member

shargon commented May 24, 2024

We need a name for D hardfork, btw. This won't be easy.

IA said: Drake, Griffin and Hippogriff. 🤣

@cschuchardt88
Copy link
Member

We need a name for D hardfork, btw. This won't be easy.

IA said: Drake, Griffin and Hippogriff. 🤣

BlockBreak, Metamorphosis

@vncoelho
Copy link
Member

Sure! It looks like you're working on a system or taxonomy for mythical creatures or something similar. You want to maintain a logical ordering or classification system for the alphabet. Here's how you might continue this:

HF_Aspidochelone
HF_Basilisk
HF_Cockatrice

Continuing in alphabetical order:

HF_Dragon
HF_Echidna
HF_Faun
HF_Gorgon
HF_Hippogriff
HF_Imp
HF_Jabberwocky
HF_Kraken
HF_Lamia
HF_Manticore
HF_Nymph
HF_Ogre
HF_Phoenix
HF_Quetzalcoatl
HF_Roc
HF_Sphinx
HF_Troll
HF_Unicorn
HF_Valkyrie
HF_Wyvern
HF_Xolotl
HF_Yeti
HF_Zephyr

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Initial issue state - proposed but not yet accepted milestone
Projects
None yet
Development

No branches or pull requests

5 participants