Beta testers?

  • 2
  • Question
  • Updated 5 months ago
Great so, we are now beta testers who pay Adobe for oportunity to test their products?!
Interesting business model.
Please Adobe we don't have time and interest to do that.
Photo of Martin Haburaj

Martin Haburaj

  • 13 Posts
  • 4 Reply Likes
  • frustrated

Posted 5 months ago

  • 2
Photo of Andrew Rodney

Andrew Rodney

  • 593 Posts
  • 104 Reply Likes
Which software product you paid for is bug free?
(Edited)
Photo of Martin Haburaj

Martin Haburaj

  • 13 Posts
  • 4 Reply Likes
haha good one :-D
but you must agree with me that LR has few ver. which was good.
Photo of avpman

avpman

  • 96 Posts
  • 63 Reply Likes
You know what he means and he's right on target. The LR CC versions are Beta at best, maybe not by intentional design but certainly by how they perform. Adobe needs to step up their internal UA testing. They've never been able to meet their commitment to putting out quality software under the CC model.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1548 Posts
  • 624 Reply Likes
I think that is the fundamental problem of the subscription system. In the past, the developers (and beta testers) could spend up to two years or more before a new version was released. That means that most of the new features would have been in beta testing for a very long time too and most of the bugs would have been found and dealt with. Only the latest new additions would not be tested so thoroughly.

With the subscription system new features are introduced roughly every two months, because that is what people pay for. But that has a downside too, that there is only a short time for testing. And sometimes new features are even half-finished because of that time frame, like the new profiles that didn't sync yet in 7.3.
Photo of Martin Haburaj

Martin Haburaj

  • 13 Posts
  • 4 Reply Likes
I don't need new features every two months, but if they are doing it like that, they may doing it properly.
Ad new feature, but basic things which is there for years is missing or stop working properly.
And we are paying it month after month.
Photo of Andrew Rodney

Andrew Rodney

  • 593 Posts
  • 104 Reply Likes
As an Adobe beta tester (for 26 years), I don't see anything fundamentally different in the process for a subscription vs. perpetual product. In fact, with the older model, were we often provided a lot of new features to test at once, unlike the more gradual provision to newer features to test. So I don't buy that based on a lot of experience. 
All software has bugs. Now if you want to suggest, the community of beta testers and the speed in which bugs are found and fix may be less effective today than a few years ago, I might agree. Each team does this differently too. I'm testing multiple Adobe products (among other companies) and some groups do this better than others. 
Photo of Martin Haburaj

Martin Haburaj

  • 13 Posts
  • 4 Reply Likes
Ok so we have a new subscription model, but software which is working good only in one ver. per year. As i say I don't need new features every two months.
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1548 Posts
  • 624 Reply Likes
Being a beta tester too, I beg to differ. In the past, a feature like the new profiles (introduced half-baked in 7.3, without sync and so causing a lot of 'profile not found' problems on mobile systems) would not have been introduced this way. 
Photo of Martin Haburaj

Martin Haburaj

  • 13 Posts
  • 4 Reply Likes
the mobile is other story but is enough if you have a working cataloge on removable storage and you want to work on it on another machine.
Photo of Andrew Rodney

Andrew Rodney

  • 593 Posts
  • 104 Reply Likes
In the past, a feature like the new profiles (introduced half-baked in 7.3, without sync and so causing a lot of 'profile not found' problems on mobile systems) would not have been introduced this way

It would have been introduced how and why is a subscription any different? 
Does Adobe get it right every time? No. Who does. 
Anyway, we have no one to blame but us beta testers unless you can tell me who flied a bug report sufficiently in advance of release that was ignored. 
Photo of Robert Somrak

Robert Somrak, Champion

  • 176 Posts
  • 47 Reply Likes
I could show you a LOT of bug reports that have been filed several releases ago on the beta forum that are repeatable, acknowledged by Adobe and acknowledged  they were an issue and would be fixed that are still in 7.4.  When the beta testers like myself that take the time to thoroughly test a problem and provide a repeatable scenario and document the bug and have it acknowledged and deemed an important issue and then to see it never fixed makes it harder for the beta testers to keep trying.  I am really liking these new features being added but there has to be a balance between features and bugs not being fixed that make the software less useable.  
Photo of Andrew Rodney

Andrew Rodney

  • 593 Posts
  • 104 Reply Likes
You are absolutely certain the reported bug was variable on multiple systems, that Adobe and others could replicate it? If so, Adobe has deliberately decided not to fix it?
Photo of Robert Somrak

Robert Somrak, Champion

  • 176 Posts
  • 47 Reply Likes
The bugs are mine and were reported on the beta forum and were acknowledged and replicated.  The statement about Adobe DELIBERATELY not fixing them is NOT in my post and hopefully I did not insinuate that.  They are probably busy fixing more important bugs and may get around to them sometimes in the future.  Feedback on bug reports could be better but that takes more time from actual fixing.
Photo of Andrew Rodney

Andrew Rodney

  • 593 Posts
  • 104 Reply Likes
Busy fixing more important bugs, that makes sense.
Photo of Robert Somrak

Robert Somrak, Champion

  • 176 Posts
  • 47 Reply Likes
I do give Adobe credit as they are more responsive to bugs than in the past and the team seems to want to provide a better product.  They have probably been overwhelmed since the release of Lr 7.   I for one would not want to go back to the perpetual release schedule and have to wait years for new features.  Releasing new features on a point cycle does undoubtedly produce more growing pains and will hopefully be a good tradeoff.