< Features
(Test plan) |
|||
| Line 25: | Line 25: | ||
== How To Test == | == How To Test == | ||
More detailed informations How To Test Matahari can be found in [https://github.com/matahari/matahari/wiki/TestPlan the Matahari Test Plan]. We are interested in a general community testing of currently available agents and core Matahari - for both local (DBus) and remote sides (QMF). We do not offer any special instruction for testing, just try to use Matahari for your tasks and report possible issues/enhancements. | |||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | ||
Revision as of 08:55, 8 July 2011
Matahari
Summary
Matahari is a collection of generically useful APIs accessible over a remote and local interfaces via a collection of Agents, and a framework for adding small set of Agents & APIs.
Owner
- Name: Jaroslav Reznik, Andrew Beekhof and the Matahari team
- Email: jreznik@redhat.com, andrew@beekhof.net and matahari@lists.fedorahosted.org
Current status
- Targeted release: Fedora 16
- Last updated: 2011-07-07
- Percentage of completion: 25%
Detailed Description
Benefit to Fedora
Scope
Currently Matahari scope is isolated as we're now working mostly on agents/interfaces side.
How To Test
More detailed informations How To Test Matahari can be found in the Matahari Test Plan. We are interested in a general community testing of currently available agents and core Matahari - for both local (DBus) and remote sides (QMF). We do not offer any special instruction for testing, just try to use Matahari for your tasks and report possible issues/enhancements.
User Experience
Dependencies
The dependencies are Qpid with QMFv2 (Qpid Management Framework).
Contingency Plan
As no packages in Fedora currently depends on Matahari we will continue with the development efforts in Rawhide.