----- Original Message -----
On Wed, 2012-01-18 at 11:16 -0500, Steven Hawkins wrote:
> Yes, anything with nested or complex tables didn't import very
> well. Also the xml examples sometimes have errors rather than
> showing the docs.
I will see if I can correct some of these then.
> For the grammar we have control over what docbook is generated, so
> I will take a look at simplifying the structure and re-import.
> Ideally we would use a process built into the release to update
Sounds good, only issue I have seen is there seems to be no import of
HTML. They support richtext or markup. We need to some how generate
> Maybe we should just lock the documentation module for now rather
> than deleting so that it will be easier to access the source until
> the docs are corrected. Will we still even need separate
> downloadable pdf docs, or will we just want to put the pdfs in the
OK, I do not think we need separate PDF downloads anymore, as any
can export these docs into PDF if they want. Yes, we need to change
release process such that at the time of release we make a copy of
sub-space and assign the release number. As per adding the PDF to
I have not seen Jboss AS doing the same, so I am OK if we do not
them anymore for ease of doing the build in one step.
If we don't add the pdfs, then we'll need to kick that task over to
productization. In the past we've been required to include the docs with the kits for
environments that are not allowed to have internet connectivity.