Posted by: Vic Iglesias | July 9, 2012

Manual testing is a key element to a hardened QA process allowing for the human mind to be used in tasks that lend themselves to critical thinking or are simply not automatable such as:

Exploratory (also called ad-hoc) which allows testers to test strange and unusual codepaths Use Case which intends to simulate as closely as possible the end to end solution that will be deployed Usablility which aims to test whether the product meets the timing, performance, and...
Posted by: Daved Federlein | July 5, 2012

In my last post I detailed how to set up your own MeetBot to log your IRC presentations.  In this post I want to discuss how to log a screen cast your demonstration shell for later viewing.  While MeetBot can log your session interactions in IRC (such as lecture/talk and questions/answers from the audience), using shell logging on the demonstration screen session can lack being able to see what happens inside an editor, for example.  This leaves the lasting record lacking for demonstrative...

Posted by: Garrett Holmstrom | July 3, 2012

All kinds of articles on the Internet tell you how to revert a range of git commits in one massive, squashed-together revert commit. But to split them up into separate revert commits you have to pass a list of commits to git revert, and that list has to go in reverse order to avoid conflicts.

git rev-list --reverse ${last_good_commit}.. | xargs git revert

Posted by: Imran Hossain Shaon | July 1, 2012

Amadeyr Cloud Ltd. a social enterprise aimed at bridging the literacy and digital divide in Bangladesh and maximizing information efficiency by the use of information technology, has signed a partnership contract with Eucalyptus Systems, creators of the most widely deployed … Continue reading →

Posted by: Kyo Lee | July 1, 2012

Had a little fun with iMovie during Eucalyptus 3.2 Design meeting week.

Posted by: Garrett Holmstrom | June 27, 2012

Now that Eucalyptus 3.1 is out at last and we all get to wade through tons of announcements and blog posts, I thought I would mention a few of the changes that have happened since Eucalyptus 2 that you aren’t likely to see in marketing materials.

Why Eucalyptus 2? Most of us don’t get to use Eucalyptus 3.0, so comparing against that wouldn’t exactly be fair, would it? ;-)

Centralized documentation

The documentation for Eucalyptus 2 was strewn about the Eucalyptus website on a...

Posted by: Rich Wolski | June 27, 2012

The release of Eucalyptus 3.1 marks the end of the beginning for Eucalyptus 3. In February of this year, we released Eucalyptus 3.0 -- a fairly extensive re-factorization of the Eucalyptus platform to support features, such as high availability, identity management, and bootable storage volumes, all of which required intrinsic changes to the implementation of the cloud fabric itself. We also needed to change the way Eucalyptus is modularized to allow easier more "pluggable" deployments and...

Posted by: Greg DeKoenigsberg | June 27, 2012

Eucalyptus 3.1 is open for business.  (Or will be shortly: still waiting for launch as of 9:23am Eastern US time.)

No more artificial separation between Enterprise and Community.  No more frenzied checkins to the “enterprise edition” while the separate-but-equal “community version” atrophies.  No more working on new features behind closed doors for months on end.  No more wondering about what’s on the roadmap.  No more going weeks without any publicly visible check-ins.  No more....

Posted by: Kyo Lee | June 23, 2012

When being interviewed at Eucalyptus, one is often asked, “when do you stop testing software?” This is not a trick question. As a matter of fact, this is not even a question; there is only one answer, and everyone knows it.

You never stop testing.

In Eucalyptus, we take the answer above very much literally.


Eucalyptus has always displayed strong interest in creating an innovative, state-of-the-art software development workflow that supports four value-driven...

Posted by: Marten Mickos | June 19, 2012

Together we can accomplish so much more. We are building an architecture of participation into and around Eucalyptus. Version 3.1, due out later this month, signals and shows this approach.

There is just one Eucalyptus platform - and it is free and open source code. You are welcome to get your own copy, play with it, modify it, and redistribute it. Even if you don't want to look into the actual Eucalyptus source code, the APIs we’ve added to the product allow you to independently...