[
https://issues.jboss.org/browse/JBOSGI-472?page=com.atlassian.jira.plugin...
]
Thomas Diesler edited comment on JBOSGI-472 at 7/6/11 2:13 PM:
---------------------------------------------------------------
Mark says
It's all explained in the Introduction section of the Authoring Guide ;)
https://docs.jboss.org/author/display/AUTHGUIDE/Introduction
"Content is authored using wiki markup in Confluence and exported to DocBook XML
whenever a project is released."
Basically you should only use Confluence for the latest version of your docs. If you
perform a release then you should export the wiki markup to DocBook XML and check it into
the SCM alongside the code as normal. You then maintain released documentation using the
SCM.
was (Author: thomas.diesler):
Marc says
It's all explained in the Introduction section of the Authoring Guide ;)
https://docs.jboss.org/author/display/AUTHGUIDE/Introduction
"Content is authored using wiki markup in Confluence and exported to DocBook XML
whenever a project is released."
Basically you should only use Confluence for the latest version of your docs. If you
perform a release then you should export the wiki markup to DocBook XML and check it into
the SCM alongside the code as normal. You then maintain released documentation using the
SCM.
Migrate documentation to confluence
-----------------------------------
Key: JBOSGI-472
URL:
https://issues.jboss.org/browse/JBOSGI-472
Project: JBoss OSGi
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Documentation
Reporter: Thomas Diesler
Assignee: David Bosschaert
Fix For: JBossOSGi 1.0.0 CR1
David, could you pls create the initial layout - I could then fill in the content.
There is a requirement however that we can have fixed docs associated with released
versions.
How would that work?
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira