Hi, +1 for an always working "master" branch.
Do your work in feature branches. Only merge when you think the changes are ready. Don't merge when you think "I am ready, but this needs testing". Regarding the testing problem in general: I would stop adding new features for a while. Spend more time in improving code quality. Try to find/create a working test suite. There will always be the problem that nobody will test your stuff. So you need a way to write tests. Yes, creating a test suite will take some time. But in the end it will improve the software quality and boost your development. Remember that you can use CI for free with GitHub. Every pull request could be automatically tested for you... +1 for a time-based release approach. PS: Debian Jessie will freeze at 23:59 UTC on the 5th of November 2014. Just a reminder if you want to see some of the recent changes in Jessie... -Thomas _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
