On Sun, Jan 3, 2010 at 6:08 PM, Matthew Woodward <[email protected]> wrote: > One of the things I think CFers are having trouble getting used to with open > source since they've grown accustomed to releases of CF every two years or > so is the notion of using interim releases of OpenBD, preferring to waiti > unitl they're blessed as "stable" with an official version number. > Personally I take the approach that if I need a new feature and it's in a > nightly build, I test my app(s) on the nightly build and if it works, it > works. I have no fear of putting it into production if I've tested and feel > comfortable with it.
Yes, I guess my history with open source (dating back into the early 90's) has led me to much the same behavior. When I was at Macromedia, I was pushing things out to production on prerelease software (Mach-II builds, back then) and at Adobe I pushed projects live on alpha builds of ColdFusion running prerelease builds of ColdSpring, Model-Glue and Transfer, and I've tended to continue that approach except with clients who are very cautious and explicitly state they only want to use "official" builds (most don't actually care about the technology details of course). > course the sooner people test things the better they get as well, so I > highly encourage everyone to grab nightlies often and give them a whirl. Indeed. I was very pleased to discover that nightly builds of OpenBD from 11/30/09 onward would run FW/1 and the FW/1 release notes specify that date in the supported platforms section. > The other thing I'm getting huge advantage from is considering the OpenBD > libraries (meaning the JARs, etc.) to be part of my applications on a > project-by-project basis, as opposed to installing a single version of > OpenBD and running all my projects off of that. Yes, I've recently switched completely to that approach with Railo and the ability to control versions and configure the "server" per application with everything still running on a single instance of Tomcat has been really valuable - as has the ability to clone an entire web application (which I was just espousing on the Railo list to someone new to the whole JEE container deployment process). When I was at Broadchoice, we built an AIR application backed by Spring / Hibernate / Groovy / JBoss and packaged it all as a WAR for deployment across the cluster. When we added an iPhone web app, powered by Railo, we simply rolled the runtime into the WAR and our deployment process didn't change at all. That would not have been possible with Adobe ColdFusion (unless we wanted to "plump" our deployment artifact from about 42MB to about 324MB :) -- Sean A Corfield -- (904) 302-SEAN Railo Technologies US -- http://getrailo.com/ An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
