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

Re-number the protocol versions to reflect the "Beta Stage" of the Maste... #8

Closed
wants to merge 4 commits into from

Conversation

DavidAJohnston
Copy link
Contributor

...rcoin Specification / Implementations

It seems logical to inform new comers that the Mastercoin Protocol is currently in the Beta stage of its development. I propose we can easily accomplish this by simply re-numbering the versions of the protocol (both past and present) to version numbers below that of 1.0

For example version 0.1 version 0.19 and version 0.2 for past versions and 0.3 for the current version. This gives the protocol enough room for growth between now and when it does reach a 1.0 stage of development.

…stercoin Specification / Implementations

It seems logical to inform new comers that the Mastercoin Protocol is currently in the Beta stage of its development. I propose we can easily accomplish this by simply re-numbering the versions of the protocol (both past and present) to version numbers below that of 1.0

For example version 0.1 version 0.19 and version 0.2 for past versions and 0.3 for the current version. This gives the protocol enough room for growth between now and when it does reach a 1.0 stage of development.
@ripper234
Copy link
Contributor

Makes sense +1

Ron Gross
Executive Director, Mastercoin Foundation
mastercoin.org | ripper234.com
Schedule my time at meetme.so/RonGross

On Sun, Dec 8, 2013 at 12:37 AM, David Johnston notifications@github.comwrote:

...rcoin Specification / Implementations

It seems logical to inform new comers that the Mastercoin Protocol is
currently in the Beta stage of its development. I propose we can easily
accomplish this by simply re-numbering the versions of the protocol (both
past and present) to version numbers below that of 1.0

For example version 0.1 version 0.19 and version 0.2 for past versions and
0.3 for the current version. This gives the protocol enough room for growth

between now and when it does reach a 1.0 stage of development.

You can merge this Pull Request by running

git pull https://github.com/DavidJohnstonCEO/spec master

Or view, comment on, or merge it at:

#8
Commit Summary

  • Re-number the protocol versions to reflect the "Beta Stage" of the
    Mastercoin Specification / Implementations

File Changes

Patch Links:

@DavidAJohnston
Copy link
Contributor Author

If no one has any objections and this seems like a clear improvement then lets go ahead and merge the pull request.

@dacoinminster
Copy link
Contributor

Sorry - I meant to comment on this earlier.

I'm worried there will be confusion, since these version numbers have been used other places besides this document. Also, this pull request missed one instance ("1.0", in one of the version descriptions). Could we at perhaps show the version numbers like "Version 0.3 (previously 1.1)" so that people who saw the old version numbers somewhere won't be confused?

@DavidAJohnston
Copy link
Contributor Author

J.R. Makes sense to me. I'll update the pull request as per your suggestion.

…ersion #'s

I've included the changes suggested by J.R. to include references to the old version #'s to avoid confusion.
@DavidAJohnston
Copy link
Contributor Author

J.R. as per your suggestion I've added the reference to the previous version numbers in order to avoid any confusion.

… the Spec

Given the Foundation has zero power over this open source project I don't think it is helpful to list the info@mastercoin.org email address in the Spec. I've instead added individuals such as Peter Todd, Ron Gross and myself for people to contact in addition to J.R.
@dacoinminster
Copy link
Contributor

Ugh. "We can’t automatically merge this pull request." from github. I'll have to use git tools to resolve the conflicts before I can merge this pull request.

@dacoinminster
Copy link
Contributor

(If somebody else wants to do it, feel free)

@DavidAJohnston
Copy link
Contributor Author

Let me know if I need to enable these somehow in the future. Happy to do so.

@dacoinminster
Copy link
Contributor

The problem is that git thinks there is a conflict which needs to be resolved, so I can't just push a button to merge your changes. I have to check out the project to my local PC, resolve whatever the conflict is, then check that in.

@dacoinminster
Copy link
Contributor

David resubmitted this after correcting conflicts, and asked me to close the old one

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

Successfully merging this pull request may close these issues.

None yet

3 participants