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

Agenda: Development, Apr 16 2019 #102

Closed
1 of 2 tasks
lehnberg opened this issue Apr 5, 2019 · 5 comments · Fixed by #112
Closed
1 of 2 tasks

Agenda: Development, Apr 16 2019 #102

lehnberg opened this issue Apr 5, 2019 · 5 comments · Fixed by #112
Labels
development Anything related to development meetings Anything related to meetings

Comments

@lehnberg
Copy link
Collaborator

lehnberg commented Apr 5, 2019

Solicit suggestions for agenda items for the Development meeting to be held on Tuesday Mar 19 @ 15:00 UTC in Grin/Dev Gitter. Please comment to provide topics or suggestions.

Proposed agenda

  1. Igno's Retrospective
  2. Agenda review
  3. Action point follow ups from previous meetings
  4. Security review status
  5. Protocol versioning & features handling
  6. Grin v1.1.0
    1. Status?
    2. On track for release the next week?
  7. Grin v1.0.3
    1. Released? Status?
  8. Wallet related issues migration to grin-wallet
  9. Other questions
@lehnberg lehnberg added meetings Anything related to meetings development Anything related to development labels Apr 5, 2019
@0xmichalis
Copy link
Contributor

Got a list of wallet issues in grin that need to be moved in grin-wallet: https://pastebin.com/AVk2MdWZ

@DavidBurkett
Copy link

I think we're handling protocol versioning & features in a non-optimal way. "Capabilities" should probably just be reserved for optional/configurable functionality (eg. full history, i2p support), whereas new functionality that we expect all up-to-date peers should support could just be identified by protocol version.

As an example, we expect all future peers will be able to offer the ability to download kernel data separately from output data (see: https://github.com/mimblewimble/grin/pull/2743/files). That should probably just result in a protocol_version bump, instead of creating a new capability. I believe this will result in simpler code over time, and also offers us the ability to do things like force really old peers to update (eg by refusing to connect to peers below a certain protocol version). I'd like to discuss this in Tuesday's meeting.

@lehnberg
Copy link
Collaborator Author

Updated agenda

@0xmichalis
Copy link
Contributor

Initial cut of the testing doc at https://github.com/mimblewimble/docs/wiki/WIP:-Release-testing

@lehnberg
Copy link
Collaborator Author

Nice, updated and also moved CI action to Quentin who's running that show now :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Anything related to development meetings Anything related to meetings
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants