[
https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313569#comment-17313569
]
ASF GitHub Bot commented on JAMES-3226:
---------------------------------------
chibenwa commented on pull request #4:
URL: https://github.com/apache/james-site/pull/4#issuecomment-812325126
```
Connecting to https://api.github.com to check permissions of obtain list of
jeantil for apache/james-site
Loading trusted files from base branch live at
cfe1da90052761ac73582d329286ca2febf28c68 rather than
e9da1975d07ca1849c6b4e45302c957aa3fd43ad
Obtained Jenkinsfile from cfe1da90052761ac73582d329286ca2febf28c68
‘Jenkinsfile’ has been modified in an untrusted revision
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Provide a process around documentation publishing and deployment
> ----------------------------------------------------------------
>
> Key: JAMES-3226
> URL: https://issues.apache.org/jira/browse/JAMES-3226
> Project: James Server
> Issue Type: Sub-task
> Reporter: Ioan Eugen Stan
> Assignee: Ioan Eugen Stan
> Priority: Major
> Attachments: Captură de ecran de la 2020-07-31 02-34-10.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> We have started working on the documentation and it's great.
> We should also document the processes around documentation:
> - when we publish the docs
> - how to publish the docs
> - where to publish the docs
> - when we retire old docs ?!
> This task should aggregate discussion and decisions.
> The process should be written as asciidoc.
> We decided to use antora as a documentation system so the features are going
> to depend on that technology.
> We should have documentation for every release we make.
> This is important since people don't upgrade immediately after release and
> might use an older release for some time.
> I'm not sure if the documentation for all versions should be online.
> We can build zip archives of each documentation release and include it in the
> binary release or publish them for download next to it.
> This way we can keep only the latest 1-3 versions online.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
