Years ago, we had automatic nightly builds. Something like this would be cool, but at least I have no time in order to setup something like this and then maintain it.
Every release involves a lot of additional work. I use several tools for static code analysis, making spell checks and of course building PixelLight across many platforms over and over again and checking those builds for obvious issues. Writing release notes and then publishing it is the smallest part of a release.
So, a two month release interval was already quite some effort for a single person to accomplish. Maybe we can share some of the work in the future, meaning that a release is announced in the forum and then several people build and test the current Git repository version and reporting back any found issues as well as reviewing the release news.
I agree that it would be fantastic if there would be more activity from the community side. For instance at GitHub
and the PixelLight Wiki
. I assume that when more people are getting active, this will motivate the rest of the developers.
In general, spreading the word about PixelLight might also help. It appears that PL is still quite unknown and as for me, I did everything I can to make it known by posting PL release notes around the net, making from time to time image of the day posts
- without starting to spam around (which we certainly should not