Minor change to avoid the potentially problematic "automating" word in the context of releases.
|Deletions are marked like this.||Additions are marked like this.|
|Line 33:||Line 33:|
|* Simplifying and automating the release procedure to allow for more frequent releases||* Simplifying the current multi-repo release procedure to allow for more frequent releases|
Status report for the Apache jclouds project - July 2014
A cloud agnostic library that enables developers to access a variety of supported cloud providers using one API.
jclouds has carried out two successful releases (1.7.2 and 1.7.3) in the last quarter and plans to release 1.7.4. The jclouds website and documentation continues to be expanded.
The developer and user community is active, with sustained activity by the core team. The PMC is still looking to grow the committer base and encourage contributions across the spectrum of supported APIs and providers.
A slightly more detailed look at the project community. It should still be brief, issues to think about include:
When was the last committer voted in?
2014-04-02 (Jeremy Daggett)
When was the last PMC member added?
2013-04-29 (initial composition of the PMC when jclouds entered the incubator)
There is regular activity on both the user and dev lists. Responses to questions are generally fast, with multiple community members contributing.
What are the projects main plans and expectations for the community in the next period?
- Simplifying the current multi-repo release procedure to allow for more frequent releases
- Determine an approximate release cadence and publish a draft roadmap
- Encourage involvement and contributions by vendors of supported providers
- Help students complete their two Google Summer of Code projects
TODO: Additional items?
Have there been any releases from the project in the last quarter?
- 1.7.2 (2014-04-16)
- 1.7.3 (2014-05-30)