Pull releases for critical bugs
The latest version of c1 has a known critical bug, yet the release is still downloadable and there is no mention of this critical bug in the release notes. This causes users who run across this type of bug (the clone variant command doesn't display background mask/adjustments on the cloned variant) to waste time trying to determine if it's a bug, filing a bug report, rolling back their installation, etc.. As soon as a critical bug such as this is discovered, the release should be pulled from the download site, and an email sent to users. We are in production environments and while there are always bugs, critical issues such as this should be handled in a different manner.
-
Could you note your Mac or Windows OS version as well as the C1 version? Much appreciated.
0 -
Hi BARRY BRAUNSTEIN I can see the bug that you reported is being worked on. Whilst this is critical for your workflow, it is not exactly "critical" as it does not impact every user or stop them from working – in this instance we would recommend that you use a version that does not exhibit this bug, until there is a fix available in an update.
If we were to pull releases from the website every time there was a bug reported, then we wouldn't be releasing very often.
But I can assure you that a fix for the bug you reported is coming soon.
0 -
I guess we have a difference of opinion on the severity of this issue, and what would constitute pulling a release. I don't know how many users are affected, nor how many use the clone variant command with background masking (I suspect it's a decent percentage) - it's helpful to know that you consider "critical" something that would stop every user from working. I would call that more "Catastrophic", all hands on deck kind of bug. And I appreciate the fact that this bug is being worked on - what I'm trying to get across is a better mechanism for at least advising users of this level of bug - I wouldn't consider this a "corner case" (but then again I'm not running your engineering organization). I'm not using the tool in a way it wasn't intended or certainly tested for - my hardware and software is pretty standard and up to date. I've already rolled back to a previous release - I'm trying to avoid (for me and others) the time involved around all this. Some software companies have a running "known issues" list published for each release. That might be something worth considering.
0 -
Robert - am running Win11, latest version with all updates and the latest version of c1 (.4 release).
0 -
BARRY BRAUNSTEIN We have the "Known Bugs" section of the forum and all known issues are communicated in the release notes. I'm not trying to downplay your issue, but just making you aware that some of these mechanisms are already in place.
It seems that you have unfortunately been highly impacted by this bug, and it is critical for you – there's no doubt about that. But yes, critical for us would be something along the lines of tethering breaking for all Windows users, just as an example.
Above all, you are certainly doing nothing wrong and it is definitely our responsibility to fix this bug.
Please let me know if you need any advice on rolling back versions and what the best path forward is. You can also make another support case, whereby they can provide advice in a more private setting and perhaps be able to tell you a little bit more about the progress of the bug being fixed.
0 -
I'm also concerned by this bug and made a regarding post here. Although it's not a critical bug for me I would call it severe and that should be listed in the Known Bugs subforum but it's not in there. It's at least imo on the same level as the bugs mentioned there.
0
Post is closed for comments.
Comments
6 comments