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

Preview4 Checklist #1936

Closed
44 tasks done
superboyiii opened this issue Sep 15, 2020 · 42 comments
Closed
44 tasks done

Preview4 Checklist #1936

superboyiii opened this issue Sep 15, 2020 · 42 comments
Labels
Discussion Initial issue state - proposed but not yet accepted

Comments

@superboyiii
Copy link
Member

superboyiii commented Sep 15, 2020

Neo3-preview4 Release Checklist

Now We're preparing the checklist of neo3-preview4 for task collection. We've already focused on these issues and PRs but we're also glad to collect other requirements. This checklist will be frozen on Dec 7th, then we'll work on these.
This release should be on 12/15 2020 (Can be moved forward if completed ahead). Then Preview4 testnet will be launched. And two weeks later, we will release neo-cli v3.0.0 and launch neo3 testnet. Formal testnet will nearly the same as Preview4 testnet, but chain data and seed nodes will be reset. Now we're focusing on these issues and PRs.

Since more PRs and Issues are coming to Checklist, we delay the release time for three weeks(12/15 2020)

Mandatory issues

Mandatory PRs

@superboyiii superboyiii added the Discussion Initial issue state - proposed but not yet accepted label Sep 15, 2020
@devhawk
Copy link
Contributor

devhawk commented Sep 15, 2020

Can we include neo-project/neo-modules#335 plus a fix for neo-project/neo-modules#343 in preview 4? Once 335 PR is in, I can do the work to fix 343 very quickly.

@vncoelho
Copy link
Member

vncoelho commented Sep 15, 2020

Looks good @superboyiii.
I agree with those two PRs, @devhawk, if you need any support let me know.

@vncoelho
Copy link
Member

vncoelho commented Sep 15, 2020

Who will proceed with "Allow oracle to access NeoFS", @roman-khimov @neo-project/ngd-shanghai? The template for the asynchronous has been merged. Will it come after we merge neo-project/neo-modules#326 or you are already preparing it?

@Tommo-L
Copy link
Contributor

Tommo-L commented Sep 15, 2020

Who will proceed with "Allow oracle to access NeoFS", @roman-khimov @neo-project/ngd-shanghai? The template for the asynchronous has been merged. Will it come after we merge neo-project/neo-modules#326 or you are already preparing it?

We'll add this feature after neo-project/neo-modules#326 merged.

@devhawk
Copy link
Contributor

devhawk commented Sep 15, 2020

I agree with those two PRs, @devhawk, if you need any support let me know.

FYI @vncoelho I had linked to the wrong PRs - the ones I was mentioning are in modules repo

@vncoelho
Copy link
Member

Then I need to double check...aehuahuea The async RPC looks good in my opinion but not necessarily a feature that we need right now. But if you have in mind a good way to distribute its loads it would be good if it can come asap.

@devhawk
Copy link
Contributor

devhawk commented Sep 15, 2020

Then I need to double check...aehuahuea The async RPC looks good in my opinion but not necessarily a feature that we need right now. But if you have in mind a good way to distribute its loads it would be good if it can come asap.

You might not need it, but neo express does.

@vncoelho
Copy link
Member

If it is a requirement perhaps it should be included.

@devhawk
Copy link
Contributor

devhawk commented Sep 17, 2020

We should have a simple Oracles sample for preview 4 developers

@devhawk
Copy link
Contributor

devhawk commented Sep 22, 2020

Can we include neo-project/neo-devpack-dotnet#362 in checklist for preview 4?

@superboyiii
Copy link
Member Author

Can we include neo-project/neo-modules#335 plus a fix for neo-project/neo-modules#343 in preview 4? Once 335 PR is in, I can do the work to fix 343 very quickly.

Done.

@superboyiii
Copy link
Member Author

Can we include neo-project/neo-devpack-dotnet#362 in checklist for preview 4?

Done.

@devhawk
Copy link
Contributor

devhawk commented Sep 22, 2020

FYI @superboyiii I added the fix for neo-project/neo-modules#343 to neo-project/neo-modules#335

@roman-khimov
Copy link
Contributor

IIUC preview4 is supposed to have broader support from various community projects, especially ones that are more developer- and user-oriented, like compilers, wallets, light nodes and alike. These tend to care more about external interfaces provided by the node rather than internal improvements, thus I'd like to raise priority for some of the issues related to these external node interfaces.

neo-project/neo-modules#354 --- this one is a MUST before preview4 to me
neo-project/neo-modules#351, neo-project/neo-modules#337 --- affecting frequently used APIs, better deal with them now than leave post-preview4
neo-project/neo-modules#358, neo-project/neo-modules#355, #1977 --- these are very important for some RPC clients
neo-project/neo-modules#334 --- minor, but easy to fix and helps a lot
neo-project/neo-modules#352 --- minor, but easy to fix

@superboyiii
Copy link
Member Author

IIUC preview4 is supposed to have broader support from various community projects, especially ones that are more developer- and user-oriented, like compilers, wallets, light nodes and alike. These tend to care more about external interfaces provided by the node rather than internal improvements, thus I'd like to raise priority for some of the issues related to these external node interfaces.

neo-project/neo-modules#354 --- this one is a MUST before preview4 to me
neo-project/neo-modules#351, neo-project/neo-modules#337 --- affecting frequently used APIs, better deal with them now than leave post-preview4
neo-project/neo-modules#358, neo-project/neo-modules#355, #1977 --- these are very important for some RPC clients
neo-project/neo-modules#334 --- minor, but easy to fix and helps a lot
neo-project/neo-modules#352 --- minor, but easy to fix

All these are added.

@Tommo-L
Copy link
Contributor

Tommo-L commented Oct 12, 2020

Add #1973, as it's imcompatible.

@superboyiii
Copy link
Member Author

Add #1973, as it's imcompatible.

Done.

@devhawk
Copy link
Contributor

devhawk commented Oct 20, 2020

Any chance of including #1966 in preview 4?

@devhawk
Copy link
Contributor

devhawk commented Oct 20, 2020

Is preview 4 the last chance for breaking changes? i.e. will we be able to consider making more changes for #1866 after preview 4? (such as #1952 and neo-project/neo-devpack-dotnet#371)

@superboyiii
Copy link
Member Author

superboyiii commented Oct 21, 2020

Any chance of including #1966 in preview 4?

Sorry, Harry. This PR is excellent but it has made huge changes, maybe we could merge it to neo-core after neo v3.0.0 released and review it step by step.

Is preview 4 the last chance for breaking changes? i.e. will we be able to consider making more changes for #1866 after preview 4? (such as #1952 and neo-project/neo-devpack-dotnet#371)

We could take it into neo-core between preivew4 and neo v3.0.0.

@roman-khimov
Copy link
Contributor

All these are added.

Hmm, I don't see neo-project/neo-modules#355 there, any particular reason for that?

@devhawk
Copy link
Contributor

devhawk commented Oct 22, 2020

Any chance of including #1966 in preview 4?

Sorry, Harry. This PR is excellent but it has made huge changes, maybe we could merge it to neo-core after neo v3.0.0 released and review it step by step.

Is preview 4 the last chance for breaking changes? i.e. will we be able to consider making more changes for #1866 after preview 4? (such as #1952 and neo-project/neo-devpack-dotnet#371)

We could take it into neo-core between preivew4 and neo v3.0.0.

#1966 has changes related to #1866 (i.e. domain model unification) and #1865 (domain model decoupling). I'm much more concerned about getting changes related to unification in before shipping v3 than decoupling. Can we do a post preview 4 PR to move types like Block and Transaction to the Neo.Models namespace?

@superboyiii
Copy link
Member Author

Any chance of including #1966 in preview 4?

Sorry, Harry. This PR is excellent but it has made huge changes, maybe we could merge it to neo-core after neo v3.0.0 released and review it step by step.

Is preview 4 the last chance for breaking changes? i.e. will we be able to consider making more changes for #1866 after preview 4? (such as #1952 and neo-project/neo-devpack-dotnet#371)

We could take it into neo-core between preivew4 and neo v3.0.0.

#1966 has changes related to #1866 (i.e. domain model unification) and #1865 (domain model decoupling). I'm much more concerned about getting changes related to unification in before shipping v3 than decoupling. Can we do a post preview 4 PR to move types like Block and Transaction to the Neo.Models namespace?

@shargon @erikzhang What's your opinion?

@superboyiii
Copy link
Member Author

All these are added.

Hmm, I don't see neo-project/neo-modules#355 there, any particular reason for that?

A mis, add it back now.

@devhawk
Copy link
Contributor

devhawk commented Nov 2, 2020

#2041 is quite simple (makes BinarySerializer class public). Can we include this in preview 4?

@superboyiii
Copy link
Member Author

#2041 is quite simple (makes BinarySerializer class public). Can we include this in preview 4?

Sure.

@devhawk
Copy link
Contributor

devhawk commented Nov 4, 2020

@superboyiii I believe neo-project/neo-modules#385 is a must fix for preview 4. Invoke script RPC method script parameter handling doesn't match between RpcClient and RpcServer

@superboyiii
Copy link
Member Author

@superboyiii I believe neo-project/neo-modules#385 is a must fix for preview 4. Invoke script RPC method script parameter handling doesn't match between RpcClient and RpcServer

Fixed in neo-project/neo-modules#386

@devhawk
Copy link
Contributor

devhawk commented Nov 11, 2020

Are we switching to net5.0 target framework across the whole neo project? If so, is this going to be in preview 4? If we make that switch in Neo.VM, that means all downstream projects have to switch as well. I tried pulling the neo.vm change into https://github.com/devhawk/neo-monorepo and none of the downstream projects compile anymore.

@shargon
Copy link
Member

shargon commented Nov 11, 2020

Are we switching to net5.0 target framework across the whole neo project?

I think that is not for preview 4

@devhawk
Copy link
Contributor

devhawk commented Nov 11, 2020

Are we switching to net5.0 target framework across the whole neo project?

I think that is not for preview 4

the net5.0 change has already been made in neo-vm project. So is the plan to create a preview 4 fork at the commit before the change was made?

@devhawk
Copy link
Contributor

devhawk commented Nov 18, 2020

I think this needs to be fixed for preview 4: https://github.com/neo-project/neo/issues/2072

@Tommo-L
Copy link
Contributor

Tommo-L commented Nov 19, 2020

I think we'd better review and merge this two incompatible PRs first. #2044 #2056

@ProDog
Copy link
Contributor

ProDog commented Nov 20, 2020

I think we'd better review and merge this two incompatible PRs first. #2044 #2056

#2044 need neo-project/neo-devpack-dotnet#388 and neo-project/neo-devpack-dotnet#391, I think we can review and merge it as soon as possible, then test it together.

@shargon
Copy link
Member

shargon commented Nov 20, 2020

neo-project/neo-devpack-dotnet#388 will be replaced by neo-project/neo-devpack-dotnet#391

@devhawk
Copy link
Contributor

devhawk commented Nov 21, 2020

#2085 looks like another issue that needs to be fixed for preview 4, but given the in-flight state of some of the NEP-17 related stuff, a fix for this might already be waiting to merge.

@lock9
Copy link
Contributor

lock9 commented Dec 4, 2020

Hello,
There are a few items not checked on this list. Is the release date going to be postponed?

@devhawk
Copy link
Contributor

devhawk commented Dec 15, 2020

I hate to add to this list, but #2151 needs to be fixed for preview 4.

I can work around #2151 in neo express by calling setMinimumDeploymentFee, but I think this should be fixed for preview 4

@kelimelogg
Copy link

is it delayed again? adverse situation for the investor

@lock9
Copy link
Contributor

lock9 commented Dec 16, 2020

@kelimelogg There are always some delays on software projects, but you shouldn't worry, they are delaying it because they want to make it right. It is a healthy delay.

image

@PsychedelicHell
Copy link

Please release Neo3 so I can sell.

@kelimelogg
Copy link

what else is expected?

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
Projects
None yet
Development

No branches or pull requests

10 participants