-
Products
JBoss Enterprise Middleware
Web Server Developer Studio Portfolio Edition JBoss Operations Network FuseSource Integration Products Web Framework Kit Application Platform Data Grid Portal Platform SOA Platform Business Rules Management System (BRMS) Data Services Platform Messaging JBoss Community or JBoss enterprise -
Solutions
By IT challenge
Application development Business process management Enterprise application integration Interoperability Operational efficiency Security VirtualizationMigration Center
Migrate to Red Hat Enterprise Linux Systems management Upgrading to Red Hat Enterprise Linux JBoss Enterprise Middleware IBM AIX to Red Hat Enterprise Linux HP-UX to Red Hat Enterprise Linux Solaris to Red Hat Enterprise Linux UNIX to Red Hat Enterprise Linux Start a conversation with Red Hat Migration services
Issue #19 May 2006
Features
- Intro to design thinking
- Better Linux release notes through design thinking
- Nashville institution influences Summit design
- (Graphic) design exposed
- Design books that inspire us
- Podcasting in open source
- The Nashville Feed: Sounds of Music City
- Lyceum: One installation, many blogs
- Release early, release often. Why?
- Fedora and Red Hat Enterprise Linux, part 1
- Nashville by day or night
- Running Linux on small servers
- FAA saves $15 million
- Video: Muvee-making with Linux and Xen
- Video: Why Red Hat is interested in virtualization
From the Inside
In each Issue
- Editor's blog
- Red Hat speaks
- Ask Shadowman
- Tips & tricks
- Fedora status report
- Podcast (XML)
- Magazine archive
Feedback
Release early, release often: Why?
Greg and Chris, together in India for FUDCon.
Greg DeKoenigsberg catches up with a member of the Fedora Project Board to talk about the "Release early, release often" principle. How does releasing software before it's been thoroughly tested actually improve the software? Couldn't that make the software more vulnerable to attacks? Chris Blizzard explains.
| Duration: | 13:54 |
| Get the audio: |
[WAV] [MP3] [OGG] 
|
