SummaryIt's no surprise that discussions on UBB.Threads are dwindling down to not much activity at all, at both
UBB.Central and here at UBB.Dev. I don't think that it'd take much at all to turn this all around, since one thing that always sparks discussion would be new releases.
I'm not saying "hey, lets demand 7.6", I'm simply pointing out that there is some code that could be cleaned up and streamlined, some modifications that could be made stock (it's happened a lot before, go look at the modifications forum here), even some style element updates.
Release ScheduleSimple things, like where introduced on a schedule back when Groupee or even MindRaven owned the product; a revision update every 6 months or so could be enough to maintain a happy consumer base.
Version Revisioning7.0 - Major Release (Major code changes)
7.1 - Minor Release (Some new features, major cleanups, etc)
7.0.1 - Bugfix or Minor Code Addition Release
7.0.1.1 - Refresh Release
One of the best versioning explanations I've come across is from
dSploit:
dSploit uses a standard practice for its versioning: major.minor.patchlevel[stage].
An increment of the major part represents a release which is not backward compatible due to its many new features, this part will change rarely. A minor release instead is used when whole new features are added. Lastly, the patchlevel is incremented when a new fix is released but no new features are added to the release. The stage indicates the stability of the release and can be "a" for alpha releases (very unstable), "b" for beta releases (almost stable but yet to be fixed) and and empty stage stands for stable releases.
One thing that has bothered me about recent releases is that "Code Refreshes" should only occur within 24 hours of a release, otherwise it should warrant a new version (see "Refresh Release" above); it causes confusion when one is trying to help a community and we're running the same version with different code (or even features).
Signing OffI'd love to see UBB.Threads regain some market share; I miss the constant communication and chatter that I helped build in the community. I hate that the only resort some major communities had was to jump ship to other products; especially since some of these started as PHP ports of UBB.Classic.
Do you have any suggestions? We'd love to hear them!
