Another month has gone by and still no updates on version 4.0. For any other developers that read this forum, you probably already know that version 4 has been touted for almost a year now as the solution to many known bugs. It has been promised to solve the terrible network adapter fingerprinting, constantly having to reactivate, bugs with the linux implementations, virtual machine issues, and many other things that are listed on this forum. If you read through the latest 20 posts on this forum, you'll see it's pretty much given as the solution to every problem - "we will fix this in TA 4.0" or "this will get better once we release version 4.0".
That's fine and good, but the problem is that this version was originally promised almost a year ago and seems to be insanely behind schedule. Here's a brief history of the communication:
December 4th, 2015nickdademo wrote:> What is the ETA of v4?Sam wrote:> A few weeks away.
December 9th, 2015Sam wrote:> Sorry guys, the 4.0 final release is coming before Christmas. If we take> time out to make & test another pre-release that date could slip.
December 23rd, 2016Sam wrote:> No, it's coming in the first 2-weeks of January. We need to do more> testing, and update the documentation.
March 27th, 2016Wyatt wrote:> We're working hard to get it out by the end of March. We're almost there.> This is a big, atypical release (because of all the things we needed to> do). Future releases won't take as long.
April 3rd, 2016Wyatt wrote:> Sorry, I should communicate *potential* release dates better. When I say> "TurboActivate 4.0 is coming at the end of March." I mean> "TurboActivate 4.0 is coming at the end of March *barring no> unforeseen complications in the rollout*".> > We had an unforeseen complication that set us a week behind schedule.
April 19th, 2016Wyatt wrote:> Yes, there's a high chance it will be released this week *barring no> unforeseen problems*.
May 13th, 2016Wyatt wrote:> We're wrapping up documentation writing and final testing.
June 8th, 2016Wyatt wrote:> It's coming soon. We're doing tests, fixing last minute bugs, writing> documentation.
July 4th, 2016Wyatt wrote:> All that remains is a couple of bug fixes and finishing the documentation.
I'm sure all the developers out there understand that things can easily slip behind schedule, but 12 months behind schedule is absolutely ridiculous! It's absurd for any software company to not release an update for almost a year. On top of that, it is seriously concerning to have all of the estimates be so far off. That either means the product had 6 months worth of bugs that needed fixing (not encouraging) or things are just so chaotic that this the team had zero clarity on when the product would actually reach the market. Your customers are seriously concerned, and I think it's important to show why.
And yes, I'm sure promises can be made about how thing will be better in the future, but it's pretty clear from above that promises don't necessarily mean much. So please finish the version that was already promised almost a year ago so that we can finally be done with all of the known bugs in the current version. It's incredibly frustrating to continue upsetting our own customers due to issues with a product that was promised to be fixed almost a year ago.
