Why it seems like just a few weeks ago I had written a similar blog posting...
We're trying something a bit new in response to customer feedback this time around. We're reintroducing the idea of a point release into the REALbasic release cycle, and r3.1 is our first attempt at it. This release fixes some issues that cropped up in r3 that we felt were important to fix ASAP.
You may be wondering a bit about what the heck this whole point release thing is, and what it means, why it happens, etc. So let me explain as best I can (remember, I'm not a marketing drone, so expect this to be technical). We're not ditching the idea of rapid release, and we're not really bastardizing the concept either. A "release" for REALbasic means that there's going to be bug fixes and new features. However, when you do that sort of thing, it takes a fair amount of time -- it has to go through QA, alpha testing, beta testing, a few kicks back and forth and so on. However, there are times when you really want to push a release out that doesn't take so long because you want it to solve some heinous issues -- that's when you use a point release.
To us, a point release is what happens when you want to address the following bugs: frequent crashes/assertions from a singular cause, data loss bugs, safe bugs with new features or case-by-case functionality issues. It's a highly-targeted release that doesn't do any new features, nor introduces any unsafe code. Taking a look at the release notes:
- 3035: Assertion in compiler on old stye constructor
- 3103: [Auto] Compiler failed assertion in Expressions.cpp:1256(2008r3)
- 3236: Cannot compile or debug a service or console application
- and so on
Frequent assertion due to an r3 code refactoring
Safe assertion fix due to r3 code refactoring
Case-by-case functionality issue
Every item on the list was something that basically had excellent bang for the buck -- very safe, and affected a large percentage of our user base.
Now, you may be wondering: how does this affect the 90-day release schedule? Well, it doesn't. At this time, a point release doesn't reset the clock for when the next release comes out -- so in this case, we released r3 on July 8th so r4 will be within 90 days of that. Not within 90 days of r3.1.
You may also be wondering how frequent a point release will be happening: not very often, hopefully! The goal is to never need a point release because the releases will be so stable. However, in the case where there's some extreme need for a point release, we'll add one. But that's not your meal ticket to ask for a point release every time we come up with a new release. ;-) We're basically going to look at bug reports within the first week or so to determine whether a point release is needed -- we're *not* going to look to lists, blog posting, forums, etc since that only represents a very minor portion of our overall user base. You should basically expect to never see a point release, and be happily surprised in the event we determine we need one, if that makes sense. :-)
Well, this is an encouraging step in the right direction.
It's nice to know that REAL is taking action on user feedback. When a company listens to its customers, the customers are generally less annoyed, and that means less complaints, which means more people may take a chance and try REALbasic out, which means more chances for sales, which means...
So yeah, it's a good thing! ;)
Spot on.
Great that quick releases are re-introduced (as opposed to rapid releases). Too bad that the bug with accented chars on the Mac slipped through which will introduce additional pain for some users... 3.2 coming soon ;-)
/msa
The 3.1 release and point release in general is a great idea. It is a way to address that a general release maybe did not address all fixes and it gives RB another kick at the cat to get a bug free release out.
Nice blend of 90 day release and 'oops, that release broke something.
It sits well from here
Good work
You say it doesn't reset the 90 day release cycle, but how does it effect people who's plans may have expired, say, between july 8th and july 22nd? Does the point release fall under the date of the original release, or of the point release?
@jdiwnab -- that's an excellent question, and one I don't have the answer to actually. I'll ask around and see what I can find out.
It's wonderful that you guys took the time and effort to put out a point release! Thanks!!!
Don't let your support plan expire and it won't be an issue. :-)
You guys are committed to doing and being the best and it shows. Please keep up the good and keep listening to your customer base.
I really like how Ubuntu handles releases. They have a rapid release program much like REAL, but every two years, they have a release that will be supported for two years, and get bug fixes along with the rapid releases for that period.
Such a program would basically answer all significant criticisms of the rapid release model. Perhaps three releases every other year, rather than four, with the third release getting extra attention and bug fixes, and ongoing bug fixes until the next such release.