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

Revert "Fix version number when psecio-parse was added" #66

Merged
merged 1 commit into from
Feb 20, 2015

Conversation

hanneskod
Copy link
Contributor

Reverts #65

In 0.5 it was actually still just parse

https://github.com/psecio/parse/tree/0.5/bin

It's just that we havn't tagged a release since 0.5, so 0.6 doesn't exist. Once #52 and #62 is merged I think we should create 0.6...

hanneskod added a commit that referenced this pull request Feb 20, 2015
Revert "Fix version number when psecio-parse was added"
@hanneskod hanneskod merged commit a2c6cf9 into master Feb 20, 2015
@hanneskod hanneskod deleted the revert-65-fix-versinon-note branch February 20, 2015 14:12
@redbeardcreator
Copy link
Contributor

I agree on the version number.

@enygma
Copy link
Member

enygma commented Feb 25, 2015

wow, really? sorry about that guys....do you think it warrants a 2.0 or just up to 0.6?

@hanneskod
Copy link
Contributor Author

0.6 is good for me. I have a feeling we will do some more bc breaking before it is time for 1.0..

@redbeardcreator
Copy link
Contributor

I would tend to agree...although I think we're getting very close.

@enygma
Copy link
Member

enygma commented Feb 27, 2015

Tagged 0.6 with loads of awesomeness :)

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.

3 participants