Tracking change and innovation in the enterprise software development community
Scaling Scrum
in the enterprise?
ScrumWorks Pro
can help.
Start a trial today
Free Book Offer
SOA Demystified
$40 Value
QCon London 2010!
March 10-12, 100
Speakers, 80 sessions,
"THE" team leads and,
architects conference.
Posted by Dionysios G. Synodinos on Jun 03, 2009
A couple of days ago InfoQ posted an article about the fact that the release notes for G1 in the latest Java update, mandated that it was to be used in production only by organizations with a Sun support contract. Following the debate and the reactions that where raised in the community, Sun has explicitly updated the release notes and has removed the controversial clause.
Danny Coward from Sun quotes the InfoQ article and suggests that it was just a misunderstanding:
The Janitor is told that an earlier version of the release notes implied that you had to have a support contract to use G1. Some certainly ran with that ball and even made a topical story out of it !
Our bad. So we made the notes clearer, because you don't need to do anything special to try it out. Unless you want your kinks fixed before everyone else gets the fixes either in the next update or in JDK 7. In which case, there is nice little program waiting just for you :)
Comparing the two versions of the release notes, it seems that Sun has changed the sentences:
Although G1 is available for use in this release, note that production use of G1 is only permitted where a Java support contract has been purchased. G1 is supported thru Sun's Java Platform Standard Edition for Business program.
With:
G1 is available as early access in this release, please try it and give us feedback. Usage in production settings without a Java SE for Business support contract is not recommended.
What do you think, could this just have been a huge misunderstanding? Why did so many try to connect it to the recent news about the aquitision by Oracle?
Consolidation and Virtualization Are NOT Enough: The Case for Non-x86
Unix, Linux Uptime & Reliability Increase While Patch Management Woes Plague Windows (Yankee Group)
Brian Marick takes us through a quick tour of the most important values and challenges to adopting Agile successfully (they aren't the typical challenges and values we hear in the community).
The line between development and architecture is tricky. Does it exist at all? Is an ivory tower actually needed? There's a balance in the middle, but how do you move from developer to architect?
The word 'authority' sometimes produces an allergic response in hard-line agilists. Freedom and authority – both are bad if misused and both are good if used in right spirit for a noble cause.
"Getting Started with Grails" brings you up to speed on this modern web framework. Companies as varied as LinkedIn, Wired, and Taco Bell are all using Grails. Are you ready to get started as well?
Those familiar with only ITIL V2 often scoff at the thought that ITIL could serve as a governance framework for SOA. With ITIL V3, the focus of the framework shifted towards service-orientation.
SpringSource CTO Adrian Colyer discusses AspectJ, SpringSource's dm Server and tc Server products, OSGi and Scrum.
Heroku's Adam Wiggins talks about Rails, Background Jobs, Add-Ons, Ruby, and how Heroku manages to work around Ruby's inefficiencies using Erlang and other languages.
For Grady Booch the foundation of a good architecture is patterns, SOA being just one of many patterns. In this Second Life presentation, Booch attempts to bring more clarity on what architecture is.
2 comments
Watch Thread Reply