[
https://issues.apache.org/jira/browse/KNOX-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandor Molnar updated KNOX-3144:
--------------------------------
+Apache Knox 3.0.0 release preparation+
We are about to cut the 3.0.0 release branch. master will move on to 3.1.0.
This issue is currently unresolved and is not automatically included in 3.0.0.
Please choose one of the following:
# If this belongs in 3.0.0: once the branch is cut, cherry-pick your commit(s)
onto the new v3.0.0 branch in addition to master. Leave Fix Version = 3.0.0 so
we can track it.
# Do nothing: we will move this issue to the next release (3.1.0) as part of
release cleanup.
If we don't hear back and see no cherry-pick, the issue will be re-targeted to
3.1.0. Thanks!
> Move Documentation Site into the Source Tree
> --------------------------------------------
>
> Key: KNOX-3144
> URL: https://issues.apache.org/jira/browse/KNOX-3144
> Project: Apache Knox
> Issue Type: Improvement
> Components: Document
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 3.0.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Let's address the cumbersome documentation site by moving to MkDocs as was
> mentioned on the dev@ list.
> This Jira will represent the initial task of creating a PR within the Knox
> repo for a feature branch that we can iterate on and replace our existing
> docs mechanism within the Apache Site svn with docs generated by MkDocs and
> published to gitpages. This will be more standard and easier to contribute to
> going forward.
> I don't want to wait until it is perfect in my repo before moving it over
> since it will take too long and I will likely move on to other things. This
> will allow us to have a bit of a Docathon to fix formatting and other issues
> with the current state of my fork.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
