And then there was one les Posted May 16, 2013 Share Posted May 16, 2013 (edited) I understand whmcs wants to progress. but i feel it would be better to fix the problems before trying to move on with new features. Dont carry known bugs into a new branch please. How I Understand this process. Beta: test & fix until stable. Release: Tested working and stable. Branch: New features as implemented. Incremental: Bug fixes of new features. This process doesn't seem to be followed properly if a new branch is still containing known issues with the previous branches. Personally, I don't care about time frames and how long it takes to push out a stable release. I do care about having a working system. I do care that a bug report is worked on and fixed. I do care that things are incorrectly carried to a new branch that have already been reported. Does anybody else have an opinion on this? Edited May 16, 2013 by CDJ Hosting Link to comment Share on other sites More sharing options...
f9dc Posted May 17, 2013 Share Posted May 17, 2013 We reported a problem where if the case of an email address does not exactly match the case used at signup (for example, BusinessName@example.com versus businessname@example.com), WHMCS will reject piped emails from the customer if "accept from known addresses" is turned on. This is infuriating for small businesses who aren't technical and don't know any better. We were told to submit it as a feature request instead. Today the 5.2.5 patch was pushed out with a bug in it. When the bug was discovered, the code was changed without a version increment, and now customers have no way of knowing whether they downloaded the buggy version or the fixed version until they get hit with the domain bug. Maybe I should submit "increment the version number each time you update a version" as a feature request. Our opinion? We were not impressed. Link to comment Share on other sites More sharing options...
WHMCS Chris Posted May 17, 2013 Share Posted May 17, 2013 f9dc, What's the ticket ID for that? Link to comment Share on other sites More sharing options...
f9dc Posted May 17, 2013 Share Posted May 17, 2013 The ticket number is LVL-563922. Link to comment Share on other sites More sharing options...
WHMCS Chris Posted May 17, 2013 Share Posted May 17, 2013 The ticket number is LVL-563922. Tickets re-opened. That's not a feature request. Link to comment Share on other sites More sharing options...
f9dc Posted May 17, 2013 Share Posted May 17, 2013 Thank you. Link to comment Share on other sites More sharing options...
And then there was one les Posted May 17, 2013 Author Share Posted May 17, 2013 Anybody else have an opinion on this? I understand people have issues with support tickets, please try and keep to the point here. If we can get some valid feedback rather than tickets not being reported to maybe we can have this dealt with once and for all. Link to comment Share on other sites More sharing options...
f9dc Posted May 17, 2013 Share Posted May 17, 2013 Anybody else have an opinion on this? I understand people have issues with support tickets, please try and keep to the point here. If we can get some valid feedback rather than tickets not being reported to maybe we can have this dealt with once and for all. My point was in agreement with you. Not only are new versions released with unresolved bugs, but when existing bugs are reported, they aren't being addressed correctly. This speaks to a lack of quality control in the development cycle, which is the root cause of your complaint. Until that lack of quality control gets addressed (and WHMCS has already taken a beating over the quality of their last several releases) the issue you describe will continue. Link to comment Share on other sites More sharing options...
And then there was one les Posted May 17, 2013 Author Share Posted May 17, 2013 Today the 5.2.5 patch was pushed out with a bug in it. When the bug was discovered, the code was changed without a version increment, and now customers have no way of knowing whether they downloaded the buggy version or the fixed version until they get hit with the domain bug. Maybe I should submit "increment the version number each time you update a version" as a feature request. You know, i do feel that point is absolutely valid. Incremental patches need some more scope to them probably another decimal to be added for fixes within fixes. I can very well see how a 5.2.5 patch being fixed after release can cause problems, especially to those that have a low rate of transactions that might not even notice a problem for several days or even longer. Link to comment Share on other sites More sharing options...
And then there was one les Posted May 17, 2013 Author Share Posted May 17, 2013 My point was in agreement with you. Not only are new versions released with unresolved bugs, but when existing bugs are reported, they aren't being addressed correctly. This speaks to a lack of quality control in the development cycle, which is the root cause of your complaint. Until that lack of quality control gets addressed (and WHMCS has already taken a beating over the quality of their last several releases) the issue you describe will continue. Sorry if that seemed to disregard your reply, it wasnt meant to at all. it was only pointing to the ticket part of it, I know your ticket needed attendance im not disputing that in any way at all, I just want to see if we can get some support on this from the community. Link to comment Share on other sites More sharing options...
WHMCS Chris Posted May 17, 2013 Share Posted May 17, 2013 Hello, This isn't something that's a new concept. This is something that's slowly being resolved internally. So we appreciate your patience as things move forward. Link to comment Share on other sites More sharing options...
Recommended Posts