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 Planning: Grin v2.1.0 #179

Open
lehnberg opened this issue Aug 20, 2019 · 14 comments

Comments

@lehnberg
Copy link
Collaborator

commented Aug 20, 2019

Planning issue for version 2.1.0 of grin and grin-wallet.

Scope freeze

As per the August 20 development meeting, deadline for scope is 15:00 UTC on August 27.

Target release date

Beta: Week of Sep 30
Release: Week of Oct 14

Discussion

Planning discussion can be had asynchronously on this issue, or in the node and wallet development sub-teams on keybase.

Priority definitions

P1 - Critical
P2 - Important
P3 - Fix if time


Milestones

https://github.com/mimblewimble/grin/milestone/14
https://github.com/mimblewimble/grin-wallet/milestone/5

Items

Make suggestions by commenting in issue, preferably with a motivation and a proposed priority.

# Priority Team Description Reference
1 P1 Node Kernel lookup API call mimblewimble/grin#3000
2 P1 Wallet Update tx confirmation status by kernel mimblewimble/grin-wallet#169
3 P1 Wallet Lifecycle wallet API mimblewimble/grin-rfcs#18, mimblewimble/grin-wallet#211, mimblewimble/grin-wallet#14
4 P1 Node Variable size kernels: Initial protocol version support for p2p messages mimblewimble/grin-rfcs#21, mimblewimble/grin#3010
5 P2 Wallet Owner/foreign API secret issues mimblewimble/grin-wallet#93, mimblewimble/grin-wallet#203, mimblewimble/grin-wallet#183
6 P2 Node Add sync_status in status Node API mimblewimble/grin#2966
7 P3 Wallet BIP39 PBKDF2 mimblewimble/grin-wallet#213
8 P3 Node Variable size kernels: Full txhashset.zip support mimblewimble/grin-rfcs#21, mimblewimble/grin#3011

Out of scope

Priority Team Description Reference Motivation
P? Node Initial i2p support mimblewimble/grin#2932, mimblewimble/grin#2712 Requires RFC
@antiochp

This comment was marked as resolved.

Copy link
Member

commented Aug 21, 2019

I believe #1 involves both wallet and node subteams as the node API will need to be extended to support this.
@lehnberg (wasn't sure if I should just update this issue in-place or ping you about it).

@antiochp

This comment was marked as resolved.

Copy link
Member

commented Aug 21, 2019

Node team would like to get the following in for 2.1.0 -

# Priority Team Description Reference
1 ? Node Add sync_status in status Node API mimblewimble/grin#2966

@quentinlesceller has the details of this - I believe impl is mainly done and its primarily a case of coordinating the release as it changes an existing API.

@antiochp

This comment has been minimized.

Copy link
Member

commented Aug 21, 2019

Node team would also like to get some subset of the functionality in place for this -

# Priority Team Description Reference
1 ? Node Variable size kernels mimblewimble/grin-rfcs#21

We would like to get this is via "protocol version support" for p2p messages at least.
We may not get the full txhashset.zip support in place by 2.1.0 but I think we're going to at least try.
Even if we just get support for p2p messages in place it gives us a good foundation to for the consensus breaking changes planned for the 3.x.x HF.

Note: Above RFC is still [WIP], hoping to have this actually finalized in the next day or so covering the breakdown of functionality described here.

@lehnberg

This comment has been minimized.

Copy link
Collaborator Author

commented Aug 21, 2019

thanks @antiochp updated #1 and added #3. Re variable size kernels, how would you breakdown the chunks into distinct tasks?

Could we for example say the work "Variable size kernels" consists of:

  1. Initial protocol version support for p2p messages
  2. Full txhashset.zip support

Where 1 has higher priority than 2 in the context of v2.1.0?

@antiochp

This comment has been minimized.

Copy link
Member

commented Aug 21, 2019

Could we for example say the work "Variable size kernels" consists of:

  1. Initial protocol version support for p2p messages
  2. Full txhashset.zip support

Yes exactly - I think its pretty much as simple as that.

@lehnberg

This comment has been minimized.

Copy link
Collaborator Author

commented Aug 21, 2019

Cool, added both: one as a P1 and the other as a P3 - feel free to correct as you see fit.

@yeastplume

This comment has been minimized.

Copy link
Member

commented Aug 26, 2019

So, for wallet this is what I have (in addition to what's already there):

# Priority Team Description Reference
1 1 Wallet BIP39 PBKDF2 mimblewimble/grin-wallet#213
1 2 Wallet Owner/foreign API secret issues mimblewimble/grin-wallet#93, mimblewimble/grin-wallet#203, mimblewimble/grin-wallet#183

(Edited a bit, I missed the fact you already had one in there)

@lehnberg lehnberg referenced this issue Aug 26, 2019
2 of 2 tasks complete
@lehnberg

This comment has been minimized.

Copy link
Collaborator Author

commented Aug 26, 2019

Updated

@hashmap

This comment has been minimized.

Copy link
Member

commented Aug 26, 2019

Initial I2P support perhaps.

@jaspervdm

This comment has been minimized.

Copy link
Member

commented Aug 26, 2019

I'd like to get these 2 issues in here as well, first one is basically done and second one should be pretty easy as well.

# Priority Team Description Reference
1 P2 Node Kernel lookup API call mimblewimble/grin#3000
2 P2 Wallet Update tx confirmation status by kernel TBD
@antiochp

This comment has been minimized.

Copy link
Member

commented Aug 27, 2019

@jaspervdm are those 2 related to item 1 on the list?

@lehnberg

This comment has been minimized.

Copy link
Collaborator Author

commented Aug 27, 2019

Updated based on discussion in /dev.
☃️ Scope for v2.1.0 is now considered frozen. ☃️

@antiochp

This comment has been minimized.

Copy link
Member

commented Aug 27, 2019

🏂

@lehnberg

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.