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, Jan 22 2019 #41

Closed
lehnberg opened this Issue Jan 13, 2019 · 3 comments

Comments

Projects
None yet
2 participants
@lehnberg
Copy link
Collaborator

lehnberg commented Jan 13, 2019

Solicit suggestions for agenda items for the Development meeting to be held on Tuesday Jan 22 @ 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
    None.
  4. Post-mainnet evaluation
    1. What went well
    2. What could have been improved
    3. Are there any immediate actions to be taken as a result?
  5. Grin v1.1.0
    1. Issue milestones?
    2. Timeline target?
  6. Add templates?
    1. Issue templates
    2. Pull request templates
  7. Co-ordination and encouragement of application development
    1. "3rd party product" group?
  8. Other questions
@antiochp

This comment has been minimized.

Copy link
Member

antiochp commented Jan 22, 2019

v1.0.1 vs. v1.1.0 ?

@lehnberg

This comment has been minimized.

Copy link
Collaborator Author

lehnberg commented Jan 22, 2019

No, v1.1.0 (I think), every time we do a bug fix we increment PATCH:

https://semver.org

Summary
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

@antiochp

This comment has been minimized.

Copy link
Member

antiochp commented Jan 22, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment