I'd like to suggest the use of minor revision numbers in Jforum releases. The most recent patches you've released for 2.1 should have (at a bare minimum) been v2.1.1, if not 2.1.2, 2.1.3, etc. What has been created here is a situation where I come on a Monday and download v2.1, and you release bug fixes with the same revision number throughout the rest of the week. On friday, I come in and have to weed through all the forum posts to see if you've released a "new version of 2.1" rather than just looking for a new minor revision number that's greater than what I'm currently running. Plus, it makes changelogs, version management and even the build process MUCH more useful. There are some great strategies if you're building with
ant for revision management. If you're not building with ant... start. LOL
You may also want to hold on to all non-critical bugs for a couple days and release them all in one minor revision. Then a few days later, collect all the bugs again and release. A lot of the bugs I've seen fixed aren't "show stoppers" by any stretch, and can easily wait a few days. If a critical bug does show up... release it when you fix it (along with unreleased patches) as a minor revision and start the process over.
Just a suggestion.
[originally posted on jforum.net by Anonymous]
