zomex Posted Monday at 06:17 PM Share Posted Monday at 06:17 PM v9 set for launch in early January, no way to report bugs, no time for developers to make changes, developers having to work during holidays for any chance of supporting v9. WHMCS's response? Quote On this 9 Series rotation, we made a conscious decision to skip a public beta and go straight to a Release Candidate. The rationale is that preparing a public beta involves documentation, support paths, and feedback loops, which take significant time and resources from both product and engineering teams. Rather than slowing down the overall timeline, we focused on delivering a more feature-rich, stable RC that brings you closer to the final experience. WHMCS 9 GA will be delivered in early January. I cannot provide an exact ETA on this. 0 Quote Link to comment Share on other sites More sharing options...
wsa Posted Monday at 07:15 PM Share Posted Monday at 07:15 PM I see, i guess you need to do all reports on the ticket system like I did already :) 0 Quote Link to comment Share on other sites More sharing options...
DennisHermannsen Posted Tuesday at 12:00 AM Share Posted Tuesday at 12:00 AM 5 hours ago, zomex said: feature-rich, stable RC lol It has tons of missing features (just look at credit notes) and shipped with hardcoded paths to /var/www/html/whmcs. Not feature rich, not stable. 1 Quote Link to comment Share on other sites More sharing options...
Administrators WHMCS John Posted Tuesday at 10:39 PM Administrators Share Posted Tuesday at 10:39 PM Hi all, We welcome bug reports via https://bugs.whmcs.com as always. This time around, we made a conscious decision to skip a public beta and go straight to a Release Candidate with 9.0. Why? Because preparing a public beta includes documentation, support paths, and feedback loops takes significant time and resources from both product and engineering teams. Rather than slow the overall timeline, we focused our efforts on delivering a more feature-rich, stable RC that gets you closer to the final experience. We didn’t make this call in a vacuum, members of our UX Research Group are instrumental in guiding the design of the Nexus Cart. We ran a closed beta with select partners and hosted live demos at CloudFest USA, where we gathered in-depth, face-to-face feedback. That input was incredibly valuable, and we used it to help shape the current WHMCS 9.0 RC. 0 Quote Link to comment Share on other sites More sharing options...
zomex Posted Tuesday at 10:40 PM Author Share Posted Tuesday at 10:40 PM 3 minutes ago, DennisHermannsen said: @WHMCS John WHMCS really goofed this RC. It's released just before the holidays and will hit stable very shortly after everyone gets back to work. I hope you understand why developers are frustrated with this. Exactly. Huge update for developers and they choose to rush it through during the holidays. No beta period 0 Quote Link to comment Share on other sites More sharing options...
zomex Posted Tuesday at 10:45 PM Author Share Posted Tuesday at 10:45 PM 5 minutes ago, WHMCS John said: Hi all, We welcome bug reports via https://bugs.whmcs.com as always. This time around, we made a conscious decision to skip a public beta and go straight to a Release Candidate with 9.0. Why? Because preparing a public beta includes documentation, support paths, and feedback loops takes significant time and resources from both product and engineering teams. Rather than slow the overall timeline, we focused our efforts on delivering a more feature-rich, stable RC that gets you closer to the final experience. We didn’t make this call in a vacuum, members of our UX Research Group are instrumental in guiding the design of the Nexus Cart. We ran a closed beta with select partners and hosted live demos at CloudFest USA, where we gathered in-depth, face-to-face feedback. That input was incredibly valuable, and we used it to help shape the current WHMCS 9.0 RC. No one is talking about Nexus @John. That's a optional feature. Us developers are frustrated about the situation due to this being a major standards update. The update itself is good, we all welcome improved standards. But almost all modules will need to be updated, you're rushing the update through as quickly as possible. To rub salt in the wounds you chose to do this during the holidays. It's so crazy it's almost laughable. And you try to justify this decision rather than accept that it wasn't a wise idea. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.