| Summary: | Create gluster-tests project repo | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Jonathan Holloway <jholloway> |
| Component: | project-infrastructure | Assignee: | bugs <bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | mainline | CC: | bugs, gluster-infra, nigelb |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-18 12:30:35 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Jonathan Holloway
2016-09-26 04:27:21 UTC
Would it make sense to call it glusto-tests rather than gluster-tests? I originally avoided glusto-tests so we wouldn't limit scope, but in retrospect, probably a good idea to keep it focused and call it glusto-tests. That'll also cover both libraries and test scripts. This is now done. Could you push a change to the Gerrit repo, like for instance a README file? Looks good. Pushed a patch to review, merged, and mirrored successfully. |