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, June 11 2019 #143

Closed
bladedoyle opened this issue May 28, 2019 · 8 comments

Comments

Projects
None yet
5 participants
@bladedoyle
Copy link

commented May 28, 2019

Solicit suggestions for agenda items for the Development meeting to be held on Tuesday June 11 @ 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. Grin v1.1.0
  6. Grin v2.0.0
  7. Review our branching model
  8. POW: Putting phaseouts on hold
  9. Other questions
@lehnberg

This comment has been minimized.

Copy link
Collaborator

commented May 28, 2019

@bladedoyle perhaps join tomorrow’s extra meeting (3PM UTC, same time as usual) in order to join in on the discussion?

@bladedoyle

This comment has been minimized.

Copy link
Author

commented May 28, 2019

Yes, thank you @lehnberg.

@lehnberg

This comment has been minimized.

Copy link
Collaborator

commented May 31, 2019

Agenda updated.

@garyyu

This comment has been minimized.

Copy link
Member

commented Jun 6, 2019

I strongly propose we define a dev branch, to be discussed in dev meeting:

https://gitter.im/grin_community/dev?at=5cf921e4bf4cbd167c3e7a01

How about define master as dev branch? to merge any reviewed PRs into master (i.e. dev branch).

  • For example, if we need 1.1.1 release, we can branch from tag 1.1.0 for it;
  • and after 1.1.1 release, if we still feel 1.1.2 release is needed, we can branch from tag 1.1.1 for it,
  • and so on.

I think we need to start shifting expectations slightly around how long it should take for a PR or new concept to go from initial introduction into fully merged and targeting a particular release.
but can’t be too long, for the inspiring the developers.

We can make it longer before it go into a release, but i think we should NOT make it longer to merge/accept it (to dev branch for example).

@quentinlesceller

This comment has been minimized.

@lehnberg

This comment has been minimized.

Copy link
Collaborator

commented Jun 11, 2019

@quentinlesceller it's actually for next week's meeting, but it wouldn't hurt raising today either.

Agenda updated.

@quentinlesceller

This comment has been minimized.

Copy link
Member

commented Jun 11, 2019

@lehnberg oups my bad :)

@tromp

This comment has been minimized.

Copy link

commented Jun 11, 2019

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