Clean up the 'Components' documentation
Bug #1651102 reported by
Julie Pichon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
The Components page at [1] could use a bit of an update. There are references to tools no longer in use (devtest?), some projects are missing entirely (e.g. tripleo-common, quickstart) and some of the descriptions could be expanded a little bit to be more friendly to people just jumping into TripleO and still getting familiar with the terminology and architecture.
| description: | updated |
| Changed in tripleo: | |
| milestone: | none → ocata-3 |
| Changed in tripleo: | |
| assignee: | nobody → Julie Pichon (jpichon) |
| Changed in tripleo: | |
| assignee: | Julie Pichon (jpichon) → nobody |
| Changed in tripleo: | |
| milestone: | ocata-3 → pike-1 |
| Changed in tripleo: | |
| milestone: | pike-1 → pike-2 |
| Changed in tripleo: | |
| milestone: | pike-2 → pike-3 |
| Changed in tripleo: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in tripleo: | |
| milestone: | pike-rc1 → queens-1 |
| Changed in tripleo: | |
| milestone: | queens-1 → queens-2 |
| Changed in tripleo: | |
| milestone: | queens-2 → queens-3 |
| Changed in tripleo: | |
| milestone: | queens-3 → queens-rc1 |
| Changed in tripleo: | |
| milestone: | queens-rc1 → rocky-1 |
| Changed in tripleo: | |
| milestone: | rocky-1 → rocky-2 |
| Changed in tripleo: | |
| milestone: | rocky-2 → rocky-3 |
| Changed in tripleo: | |
| milestone: | rocky-3 → rocky-rc1 |
| Changed in tripleo: | |
| milestone: | rocky-rc1 → stein-1 |
| Changed in tripleo: | |
| milestone: | stein-1 → stein-2 |
Revision history for this message
| Emilien Macchi (emilienm) wrote Cleanup EOL bug report | #1 |
| Changed in tripleo: | |
| importance: | Medium → Undecided |
| status: | Triaged → Expired |
To post a comment you must log in.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE