Product docs (e.g. install guide, upgrade procedure, CLI guide) are version-specific. However, the current upstream docs are stored on wiki and not well versioned. Some pages contain information about multiple versions which can be confusing to read. It is better to convert these docs into Markdown docs in GitHub so the content will match the code in the same git branch. The use of Markdown in GitHub allows the doc to be read and updated with a browser like wiki.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue set to the milestone: 0.0 NEEDS_TRIAGE
Although this is more of a "Task" than a "Bug", in the PKI Team Meeting of 20171130, it was determined to place this in 10.6 - critical to provide greater visibility.
Metadata Update from @mharmsen: - Issue priority set to: critical - Issue set to the milestone: 10.6 (was: 0.0 NEEDS_TRIAGE)
Metadata Update from @edewata: - Issue priority set to: major (was: critical)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2978
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.