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

[Q] release process/policy? #11

Closed
indeyets opened this issue Nov 13, 2013 · 1 comment
Closed

[Q] release process/policy? #11

indeyets opened this issue Nov 13, 2013 · 1 comment
Milestone

Comments

@indeyets
Copy link
Contributor

@wikier what is your approach to releases?

the changelog is already quite large, but code wasn't seriously tested (I guess I'll switch my efforts to the testing). If tests prove that code works, then this version will be suitable for my use-case.

Did you see the topic in the mailing list? (by the way: is it better to post questions here or there?) Do you think that is a good idea? If it is, should it be implemented in 1.6 or 1.7 would be better? (I suppose you use something like http://semver.org/ — correct me if I'm wrong)

@indeyets
Copy link
Contributor Author

@wikier wikier added this to the 1.6.0 milestone Jul 20, 2014
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

No branches or pull requests

2 participants