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

Open Definition versioning: cleaner approval process, overall revisions #130

Open
wants to merge 2 commits into
base: gh-pages
Choose a base branch
from

Commits on Oct 9, 2015

  1. cleaner approval process, overall revisions

    It makes no sense for a "release candidate" phase to have all of: a delay before a vote, and a vote, and an announcement, and a wait period, and another vote. The summary of the text from my update is:
    
    * consensus seems apparent (no issues outstanding)
    * do immediate vote on release candidate (no delay, no extra announcements)
    * announce the release candidate, have delay, accept typo fixes, *readily* move back to earlier stages to create newer release candidate if issues come up
    * when through this without issues, then final vote
    
    Basically, there's no reason to be so hesitant to get to release candidates, do them OFTEN, quickly, once known issues are done, and then don't push them through so hard.
    wolftune committed Oct 9, 2015
    Configuration menu
    Copy the full SHA
    e288388 View commit details
    Browse the repository at this point in the history

Commits on Nov 6, 2015

  1. substantial fixes, issues > concerns, clarity

    Split up more steps, clarified many previously confusing items, emphasized the idea of deciding a scope to be addressed for each release.
    wolftune committed Nov 6, 2015
    Configuration menu
    Copy the full SHA
    3b2bd0b View commit details
    Browse the repository at this point in the history