Skip to main content
R
RobWala
Participant
September 13, 2011
Question

Unverified bugs in ColdFusion Builder bugbase

  • September 13, 2011
  • 1 reply
  • 1311 views

Is anybody working on ColdFusion Builder 2 bugs? I submitted a couple of bugs to the bugbase  (https://bugbase.adobe.com) back in May (2011) and they are still sitting in an 'unverified' state. What gives?

This topic has been closed for replies.

1 reply

A
Adam Cameron.
Inspiring
September 13, 2011

As far as I can gather, Adobe are not continuously developing CFB.  They do a release... then seem to vanish for a while (I presume get put onto other teams)... then come back again when the next release project gets under way.  The exception to this would be for hotfixes, but those'd only be released if there was a serious stability or security issue, I reckon.

Aside from that, they're not so good at keeping the bugbase up to date.  I've seen issues in there (albeit for ColdFusion, not CFB), which according to the bugbase are still seemingly untouched, however they've actually been fixed and released.

The public-facing bugbase is a new thing for them, and I don't think they've quite sussed out how to manage it yet (probably from a resourcing POV than anything else - but that's a guess), from the perspective of the clients who use it.

So... bottom line... don't put too much stock on the feedback in the bugbase, and definitely don't hold your breath for a fix to show up!  You'll probbaly need to wait until at least CFB 3.0 (or 2.x, whatever) before seeing any movement.

--

Adam

R
RobWalaAuthor
Participant
September 13, 2011

Thanks Adam. That is about what I expected, although I must say Adobe's lack of response to issues in a recently released (and purchased!) product is quite disappointing.

A
Adam Cameron.
Inspiring
September 13, 2011

Thanks Adam. That is about what I expected, although I must say Adobe's lack of response to issues in a recently released (and purchased!) product is quite disappointing.

Well I think if they promote the fact they have a public bugbase, then they kinda have a burden to then actively maintain it as a communications channel.  I think they're letting themselves down a bit there.  Their communications on the bugbase is very poor compared to other companies who maintain similar systems.

I have no problem with the timeframes for sorting out the issues though.  Well: in that just because I think an issue is important doesn't mean that in the bigger scheme of things for them they need to treat it as importantly as I'd like them to, if that makes sense.

--

Adam

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices