- Joined
- Feb 6, 2008
- Messages
- 37,743
- Reaction score
- 2,485
- Points
- 203
- Location
- Wolfsburg
- Preferred Pronouns
- Sire
OK, in that case there's not much that can be done. The newer stuff in the SVN repository already makes use of the new meshes/textures.
There is something that can be done. A new release.
What about the following plan:
- We use the next week (or so) for simply doing code reviews on the trunk. Anybody may take part. Who rather wants to work on new features, no problem. I will pick some files and do nothing else but work on quality assurance there. I will look for dodgy code, write missing comments, ask questions if I fail to understand what purpose a function has.
- At the end of the week (or so), we (or I) will make a new production branch for the next release. We will use this production branch only for bug fixes towards the next release and will not bother about features. Every friday we will make a new release from this branch. Even if it is still buggy. Rain or shine.
For the second stage, we will need testers. I will not stop somebody from implementing new features on the trunk, but I would like to have somebody who a) works on the trunk and b) is volunteering for reintegrating bugfixes from the release branch back into the trunk, so the effort is a bit longer lasting. I will keep focus on the release branch for a while.
I lack the time for some bigger SSU work, but that doesn't mean I can't do the small stuff - and if it is just bugfixing for a weekly "banana release".
Also, I would like to see the code reviews to continue for a while on the trunk for improving code quality. Maybe we could also have a "file/class of the month" in the forum for performing a public code review so more people can participate. But this would make sense once we have at least minimal code formatting standards implemented - especially the lack of comments and source code documentation makes this currently difficult.
Last edited: