Showing headlines posted by jzb

The Alpha release contains all the exciting features of Fedora 21?s products in a form that anyone can help test. This testing, guided by the Fedora QA team, helps us target and identify bugs. When these bugs are fixed, we make a Beta release available. A Beta release is code-complete and bears a very strong resemblance to the third and final release. The final release of Fedora 21 is expected in December.

Apache CloudStack, the mature, turnkey Open Source cloud computing software platform used for creating private, public, and hybrid cloud environments, today announced Apache CloudMonkey v5.2.0, the latest feature release of its command line interface tool.

The Apache CloudStack project is pleased to announce the 4.2.1 release of the CloudStack cloud orchestration platform. This is a minor release of the 4.2.0 branch which released on Oct 1, 2013. The 4.2.1 release contains more than 150 bug fixes. As a bug fix release, no new features are included in 4.2.1.

Ten years ago today, Bill Nottingham announced the release of Fedora Core 1 to the newly minted Fedora Announce list. To celebrate the 10th anniversary of Fedora, we’re going to be doing a monthly series of retrospectives and features about the Fedora Project – starting with a look back at Fedora through the eyes of the Fedora Project Leaders(FPLs).

I have an interest in application deployment systems, having created three different application bunding system (1,2, 3). These were all experiments in the area of desktop applications, but recently there has been some interesting motions in related areas, namely Docker.

Bug 1,000,000 was filed today by Anton Arapov in Red Hat’s Bugzilla. The bug, an improvement request for the automatic bug detection and reporting tool (abrt), is a nice milestone just a few weeks ahead of the 15th anniversary of Bugzilla’s first release.

The community is busy working on 4.2.0, and there's much to be done before the release is ready. This week, we're taking a look at some of the interesting discussions going on in the the community about the next generation of Apache CloudStack, and functionality we can provide, as well as procedural changes that everyone should be aware of.

It's been another busy week for the Apache CloudStack project. This week we welcome another new committer, work continues on 4.1.1 and 4.2.0, and we have some interesting discussions on how we should release the CloudMonkey and Marvin tools used with CloudStack. We've also seen a few interesting marketing discussions, and the community is gearing up for the second CloudStack Collaboration Conference taking place 23 June through 25 June in Santa Clara, CA.

We’re pleased to announce that the Call for Proposals (CfP) for the second CloudStack Collaboration Conference is now open! The conference is being held in Santa Clara, CA from Sunday June 23 through Tuesday June 25.</p> The Collaboration Conference will feature tracks for users, developers, and integrators of Apache CloudStack. We’re looking for presentations that provide insight into best practices in deploying and developing Apache CloudStack. </p>

There’s a great meme going around about geeks and repetitive tasks. Because geeks will often get annoyed at the effort of doing something manually, they often decide to find a way to automate it – which usually involves a lot more effort than doing it the one time but “geeks win, eventually” because they save time in the long run. But in the long run we’re all dead. Then what? Who knows how to run your script? What happens when it needs to be maintained? As Jon Udell points out, it’s really not a contest, it’s a process, and non-geeks can play too. Which is why you should also write it down if you’re going to do it more than two times.

The Apache CloudStack project is pleased to announce the 4.0.2 release of the CloudStack Infrastructure-as-a-Service (IaaS) cloud orchestration platform. This is a minor release in the 4.0.0 branch, which contains fixes for 40 bugs.

This time around, we have two release VOTEs in progress, which means that 4.1.0 is just about out the door. The CloudStack Collaboration Conference 2013 has been announced for June 23rd through 25th. You'll also want to check in on the discussions about the length of the release cycle, Chip Childers and David Nalley appearing on FLOSS Weekly, and much more.

A lot has happened since the last issue of the CloudStack Weekly News, and not just because the community's been busy -- we missed getting last week's issue out. Sorry about that! If you'd like to see consistent weekly delivery, check the end of the newsletter to see how you can help.

The Apache CloudStack community has been heads-down for the last week working out the remaining bugs for the 4.1.0 release. Chatter on the dev@ mailing list has been a little muted, comparatively, but there's still plenty of interest in this week's roundup of major discussions and CloudStack community activity. This week, we look at the outstanding issues for 4.1.0, a discussion about allowing multiple API names for the same API Cmd object, how to deal with tests that expect no database, and how ticket assignment should work.

Welcome to the April 1 issue of the Apache CloudStack Weekly News. Don't worry, no foolishness in this issue – just a quick recap of the week's most important events. As you recall, we officially announced that the CloudStack project was graduating from the incubator last week. Though there were no events quite of that magnitude this week, there was plenty of discussion of new features, a new Website design proposal, and Chiradeep Vittal has unveiled a new tool for testing and development called QuickCloud that will come in handy for many CloudStack contributors and users.

Apache CloudStack has graduated from the Apache Incubator! The Apache Software Foundation (ASF) board met on Wednesday (March 20) and voted in favor of the project's graduation from the incubator. The official announcement was released on Monday, March 25, 2013.

Of course, that's not all that's happened. in the past week. Work on the 4.1.0 release continues, with the first RC date slipping slightly due to the number of blocker bugs. The good news is that a lot of progress has been made on the blocker bugs in the past week, so things don't appear to be too far behind.

The board voted last week, but the announcement came out today, so it’s officially official: Apache CloudStack is now a top-level project under the Apache Software Foundation (ASF). In the grand scheme of things, this may not sound like a big deal – the ASF announces new TLPs pretty often, and Apache currently boasts more than 100 TLPs. But a fair number of projects don’t make it, and the amount of work required for a project to go from incubation to graduation isn’t trivial.

The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of nearly 150 open source projects and initiatives, announced today that Apache CloudStack has graduated from the Apache Incubator to become a Top-Level Project (TLP), signifying that the project's community and products have been well-governed under the ASF's meritocratic process and principles.

Big news this week: Apache CloudStack has passed major milestones towards graduation, major progress on bugs against 4.1.0, discussions about integrating the Palo Alto firewall with CloudStack, and getting Eclipse and Maven to play nice for developers. Some interesting posts from members of the Apache CloudStack community as well.

This week the project started the vote to determine whether the Apache CloudStack project feels ready to self-govern, discussions were held about implementing BVT (and how), and the PPMC announced its consensus for the proposed PMC chair. In addition, several technical discussions for features and processes within the project, and discussion on the -marketing list about the design of the Web site.

This week, a vote on updating the project bylaws, fixing the "Tomcat situation" after 4.1, and discussions around the support lifecycle. Some respectable progress in knocking out major and blocker bugs for 4.1.0 as well. The project also welcomes two new PPMC members and three new committers.