Adam Bien's Weblog
Why You Should File Bugs - The NetBeans Case
I used the various milestones, the beta and some daily builds of NetBeans 6.8 for my Java EE 6 projects. Sometimes NetBeans detected "slowness" (by e.g. opening 40 projects, or switching between project groups) and encouraged me to report it - what I actually did. It was more a revenge, than a goodwill :-). The first reports were anonymous, than I created an account to be able to track the progress.
With the release of NetBeans 6.8 a nice email arrived in my mailbox:
"...In the past you have taken the time to report issues that you encountered while using NetBeans software. A new version (NetBeans 6.8) has just been released,and we'd like to inform you that the following issue(s) you reported have been addressed in the new release:
|170419||Invoking Run took 29110 ms.|
|171690||Invoking Close Project took 4127 ms.|
|171756||IllegalStateException: Adding stacktrace with timestamp 4999072337859 is not allowed after a stacktrace with timestamp 4999072745299 has been added|
|172057||AWT thread blocked for 23711 ms.|
|174278||AWT thread blocked for 5513 ms.|
The NetBeans Team"
It seems like some of the issues were actually fixed. The FCS is indeed significantly faster, that the pre-release builds.
The NetBeans issue tracking tool really rocks. You get immediate feedback whether it is a new bug, a known one or what the resolution is ...without leaving the IDE.
NEW Special Events: From HTML 5 over Java EE App Building and NoSQL / Distributed Computing to Microservices