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.

Sign up for GitHub

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

Jump to bottom

automatic testing and release #35

Closed
smiller171 opened this issue Sep 30, 2015 · 2 comments
Closed

automatic testing and release #35

smiller171 opened this issue Sep 30, 2015 · 2 comments

Comments

@smiller171
Copy link

It would be useful to have an automated testing and release setup so that the latest features can be tested more easily. I could help you set this up in Travis pretty easily.
@fboender
Copy link
Owner

fboender commented Oct 3, 2015

Hey Scott,

Thanks for the offer! Given the current size of the project and the number of core committers (me ;-) I don't really think it's worth the effort to maintain another build system. The Makefile serves me fine right now. As for testing the latest features by end-users; I'd rather they use released packages. If they still wish to run against master, that's their choice of course, but I don't want to have to provide support for unreleased features.

@fboender fboender closed this as completed Oct 3, 2015
@smiller171
Copy link
Author

Typically it's better not to merge to master until code is ready for release, and Travis would do your builds for you (using your makefile)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fboender @smiller171