Report It!
This is definitely a small rant. If you're part of the CFML community, it behooves you to report issues as you find them. I really don't care which CFML engine you run. Here's a link to ALL of the engines in alphabetical order and their relevant bug tracking and mailing lists.
- Adobe ColdFusion
- Website
- BugTracker (ColdFusion)
- BugTracker (ColdFusion Builder)
- Feature Request (Use above links)
- OpenBlueDragon
- Website
- BugTracker
- Mailing List
- Feature Requests (Use above BugTracker link)
- Railo
Seriously, if you find an issue. Report it. Find out if it's a known issue. Talk to someone. Closed source, Open source... it doesn't matter. Do the CFML Community a favor and report the issue if it doesn't already exists. Yes, I realize that writing up a ticket takes time. I also know that some of the companies above move a little faster when fixing bugs / releasing patches.
/rant off
Matt Woodward wrote on 08/18/10 11:41 AM
I second this rant wholeheartedly! :-) This is the #1 way I tell people they can help these respective products/projects is to let the teams behind them know what problems they're having and what they'd like to see.Perfect example is I this:
http://blog.bayornet.com/post/railo-express-to-the-rescue
I just happened to come across that post in a Google search or something. Note the "Fix bug in CFPOI" comment. It would be GREAT if I knew what the bug was so I could fix it in the project and others could benefit, but if people keep this kind of stuff to themselves, that's just plain selfish in my opinion.
Not picking on Darren in particular but I thought that was a perfect example of what you're ranting about.
Take the 2 minutes to let someone know when you're having problems, or if you dream up a feature that would make your life easier. It's the simplest and best way to make a difference for everyone in the community.