Known Issues page
What is it?
-
New content -
Update existing content
Metadata
- Maintainer: @valentindavid
- Milestone: %BuildStream_v1.2
- Follow up from:
- This blocks: #3 (closed)
- Web page
- Target audience: users (integrators and developers)
- Topic:
-
Community -
Management -
Promotion -
Code and metadata -
BuildStream description -
Outcomes -
Landing/Project page -
Other
-
Rationale
The content design document express the purpose of this content unit in the following terms:
R.5 Known issues
On every release, there are problems that has been identified by those working on the project and not yet resolved. In some cases, there are workarounds available. This page will include such information, specially valuable prior or immediately after a release. This content should provide context/summary of what is already available on the ticketing system.
Content structure and description
This page should be structured per release. It should contain the list of issues affecting a specific release that users will hit in very early stages of the installation or very early usage of BuildStream.
- Each issue should have a link to the ticket and a short description.
- The ticket listed should have a more detailed description.
- They should well maintained to provide an idea that the developers care and understand this is impacting the user.
Technical work
-
Can we have a live state of the tickets on the website? - If yes, this page belongs to the website
- If not, this page belogs to the Gitlab wiki
-
Format correctly the items on the list.
References
Edited by toscalix