Log in
Register
Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Eric Hill - USA" data-source="post: 65162" data-attributes="member: 2100"><p>re: X32 Discussion</p><p></p><p></p><p></p><p>That cat is already out of the bag.</p><p></p><p>If they want, they'll just find another way to distribute pre-release versions to people doing testing. Or, maybe not. Maybe they’ll leave it alone for people quick enough to figure it out.</p><p></p><p>Problem is... If a tester found a problem, that Behringer subsequently fixed before public release... Would they call it 1.09 or 1.10 (and skip 1.09)?</p><p></p><p>If I were Behringer, in that case, I would skip 1.09, and call it 1.10. (Either that, or 1.09.01 or 1.09a.)</p><p></p><p>Once a version has even been made semi-public, its version reference should be set in stone.</p><p></p><p>I do like Behringer's "release early, release often" model.</p><p></p><p>That said, unless I have an immediate problem, I usually let updates sit for awhile.</p><p></p><p>The cutting edge can sometimes be the bleeding edge. (This isn't a knock on Behringer, at all. There's just a big difference between the results from a handful of testers, and the results from thousands of end-users.)</p><p></p><p>Eric H.</p></blockquote><p></p>
[QUOTE="Eric Hill - USA, post: 65162, member: 2100"] re: X32 Discussion That cat is already out of the bag. If they want, they'll just find another way to distribute pre-release versions to people doing testing. Or, maybe not. Maybe they’ll leave it alone for people quick enough to figure it out. Problem is... If a tester found a problem, that Behringer subsequently fixed before public release... Would they call it 1.09 or 1.10 (and skip 1.09)? If I were Behringer, in that case, I would skip 1.09, and call it 1.10. (Either that, or 1.09.01 or 1.09a.) Once a version has even been made semi-public, its version reference should be set in stone. I do like Behringer's "release early, release often" model. That said, unless I have an immediate problem, I usually let updates sit for awhile. The cutting edge can sometimes be the bleeding edge. (This isn't a knock on Behringer, at all. There's just a big difference between the results from a handful of testers, and the results from thousands of end-users.) Eric H. [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!