The g-Eclipse project aims to build an integrated workbench framework to access the power of existing Grid and Cloud infrastructures. The framework will provide tools to customize Grid users' applications, to manage Grid resources and to support the development cycle of new Grid applications. The same applies to Cloud Computing. The project will aim for general Grid workbench tools that can be extended for many different Grid middlewares (such as gLite, UNICORE, Globus toolkit) and interfaces to Cloud Computing, starting with implementations for the gLite middleware and the Amazon webservices (S3, EC2). The project will use existing Grid and Cloud infrastructure from projects like EGEE or Amazon After the project, access to the power of Grid and Cloud infrastructures will be more intuitive and simpler than it is possible nowadays. Grid and Cloud application users will be able to access the Grid and Cloud with standardized, but customized user-friendly interfaces Grid resource providers can reduce the cost of operation while the complexity of the Grid is reduced with supporting tools Grid application developers will be empowered to speed up the development cycle of new Grid applications The g-Eclipse project delivers the g-Eclipse framework which includes the core middleware-independent functionality without connectors to a specific middleware and an exemplary implementation for AWS. Implementations for other middlewares are available from external sources either from the g-Eclipse team itself or by other teams. The g-Eclipse team delivers one milestone release at the end of every month. June milestone July milestone August milestone September milestone October release candidate November release candidate December release candidate The final g-Eclipse version 1.0 is was planned for December 2008 but was delayed for IP reasons. Now that all IP issues could be solved the release is re-scheduled for December 2009. g-Eclipse runs on Windows 32-bit, Linux 32-bit and 64-bit, Mac OSX, is tested by the team on those platforms and requires a JVM 1.5 or higher. g-Eclipse bundles are internationalized. The g-Eclipse team provides an English version by default. While the goal of g-Eclipse 1.0 is the full backward compatibility to g-Eclipse 0.5 there will be changes in the model and in the project layout that require a new setup and a new project creation. All of those major changes they will be announced in the new and noteworthy of the release and discussed on the developers mailing list. With version 0.5, the g-Eclipse team delivered a framework for accessing Grids independent from the underlying middleware; this included the basic functionalities beginning with resource handling (data and job) up to AAI (authentication and authorization infrastructure). Following this approach, g-Eclipse version 1.0 will be enhanced to be able to work with Cloud computing infrastructures as well. Other tooling like a workflow editor will be added to the the UI and integrated into the framework. Very often we see that there is confusion about the scope of g-Eclipse. g-Eclipse is not another Grid middleware or a system that runs on the Cloud. It is a front-end tool that can be compared to a web browser that assists a user, a developer, or an administrator to work with the Grid and with the Cloud and hides the complexity of these systems. Enable the launch of workflows on the Grid and create a Workflow Editor that allows to create and execute multiple Grid jobs that are depend on each other. The Simple Storage Service (S3) will be integrated into the framework and the necessary connectors will be provided. The Elastic Compute Cloud (EC2) service will be integrated into the framework and the necessary connectors will be provided.