[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313593#comment-17313593 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil commented on pull request #5: URL: https://github.com/apache/james-site/pull/5#issuecomment-812335995 I pushed 7f7a77b95 at https://github.com/jeantil/james-site/tree/automatically-publish-staging-documenttion-on-james-project-build which should fix it not sure if I should reopen a PR or let you fetch from my fork and push here -- 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
Re: [BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]'
Hi Jean, Le 02/04/2021 à 02:52, Jean Helou a écrit : > Hi all, > > Sorry about the spam, I opened a PR to try and improve the build flow for > james documentation to try and get the staged documentation published > automatically after each build of james project. I think we need to update James site asf.yml to report github comments in the JIRA worklog just like we do for other projects, this will efficiently reduce the spam. I opened https://github.com/apache/james-site/pull/6 regqrding this. > > Unfortunately the Jenkinsfile currently in the staging branch of james-site > is out of date (the JDK name has changed) and It took me these 5 tries to > realize that none of the changes I was making to the Jenkinsfile were > accounted for because: > > ‘Jenkinsfile’ has been modified in an untrusted revision > > > I'm not sure what the best way to proceed is : this limitation can be > disabled (would be easiest since I may have further adjustments to make), > or an official apache committer can push to an alternate PR to get it to > build with the changes. > Note that in this change I have also changed the email notifications to > only notify the list for the live and staging branches and notify the > requester for other branches. I opened a branch from my fork where I will mirror changes on your branch. This will allow modifications to be trusted. CF: https://github.com/apache/james-site/pull/5 BTW you have q groovy error to fix ;-) > > best regards > jean > > On Thu, Apr 1, 2021 at 9:43 PM Apache Jenkins Server < > jenk...@builds.apache.org> wrote: > >> BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]': >> >> Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/5/;>james/ApacheJames-Website/PR-3 >> [PR-3] [5]" >> >> - >> To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org >> For additional commands, e-mail: server-dev-h...@james.apache.org > - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313591#comment-17313591 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil commented on pull request #6: URL: https://github.com/apache/james-site/pull/6#issuecomment-812334610 oh yes please event if the build is red (because the jdk name changed) -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313590#comment-17313590 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil commented on pull request #5: URL: https://github.com/apache/james-site/pull/5#issuecomment-812334337 thanks @chibenwa do you mind changing the job configuration to build PRs from untrusted sources for the moment ? this way I can debug my jenkins jobs before bothering you ... -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313588#comment-17313588 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil commented on pull request #3: URL: https://github.com/apache/james-site/pull/3#issuecomment-812332893 So I assume maintainers of this repo are the same as for the james-site repo : @chibenwa @Arsnael @mbaechler -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313587#comment-17313587 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil closed pull request #3: URL: https://github.com/apache/james-site/pull/3 -- 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
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-6 [PR-6] [1]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-6 [PR-6] [1]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-6/1/;>james/ApacheJames-Website/PR-6 [PR-6] [1]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313579#comment-17313579 ] ASF GitHub Bot commented on JAMES-3226: --- chibenwa opened a new pull request #6: URL: https://github.com/apache/james-site/pull/6 …re emails -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313576#comment-17313576 ] ASF GitHub Bot commented on JAMES-3226: --- chibenwa commented on pull request #3: URL: https://github.com/apache/james-site/pull/3#issuecomment-812326395 I opened a trusted version of this work here: https://github.com/apache/james-site/pull/5 -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[
https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313575#comment-17313575
]
ASF GitHub Bot commented on JAMES-3226:
---
chibenwa commented on pull request #5:
URL: https://github.com/apache/james-site/pull/5#issuecomment-812326160
```
Connecting to https://api.github.com to check permissions of obtain list of
chibenwa for apache/james-site
Obtained Jenkinsfile from
e9da1975d07ca1849c6b4e45302c957aa3fd43ad+cfe1da90052761ac73582d329286ca2febf28c68
(c661365bf415906054084c8c98a702f0594e9909)
Running in Durability level: PERFORMANCE_OPTIMIZED
GitHub has been notified of this commit’s build result
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup
failed:
WorkflowScript: 93: Expected a step @ line 93, column 13.
if (env.BRANCH_NAME == "live" ||env.BRANCH_NAME == "staging")
{
^
WorkflowScript: 131: Expected a step @ line 131, column 13.
if (env.BRANCH_NAME == "live" ||env.BRANCH_NAME == "staging")
{
^
2 errors
at
org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at
org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
at
org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
at
org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
at
org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
at
groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
at
org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142)
at
org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:571)
at
org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:523)
at
org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:337)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE
```
CC Jeantil
--
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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313574#comment-17313574 ] ASF GitHub Bot commented on JAMES-3226: --- chibenwa opened a new pull request #5: URL: https://github.com/apache/james-site/pull/5 Trusted version of #3 -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313572#comment-17313572 ] ASF GitHub Bot commented on JAMES-3226: --- chibenwa commented on pull request #4: URL: https://github.com/apache/james-site/pull/4#issuecomment-812325463 Closing as itis still untrusted. I will retry with a branch started from a HEAD of my repo. -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313570#comment-17313570 ] ASF GitHub Bot commented on JAMES-3226: --- chibenwa closed pull request #4: URL: https://github.com/apache/james-site/pull/4 -- 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
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313568#comment-17313568 ] ASF GitHub Bot commented on JAMES-3226: --- chibenwa opened a new pull request #4: URL: https://github.com/apache/james-site/pull/4 Trusted version of https://github.com/apache/james-site/pull/3 -- 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
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-4 [PR-4] [1]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-4 [PR-4] [1]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-4/1/;>james/ApacheJames-Website/PR-4 [PR-4] [1]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3434) [JMAP] Send: EmailSubmission/create (user email)
[
https://issues.apache.org/jira/browse/JAMES-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313566#comment-17313566
]
Benoit Tellier commented on JAMES-3434:
---
@InputMice, behind the LTT.RS mobile app did perform a bug report on linagora
bug tracker. I share it here:
https://github.com/linagora/james-project/issues/4310
In brief, Re-reading https://jmap.io/spec-mail.html#emailsubmissionset
I was convinced it was taking emailId (symetry with onSuccessDestroyEmail), I
must admit I am wrong...
```
onSuccessUpdateEmail: Id[PatchObject]|null A map of EmailSubmission id to an
object containing properties to update on the Email object referenced by the
EmailSubmission if the create/update/destroy succeeds. (For references to
EmailSubmissions created in the same “/set” invocation, this is equivalent to a
creation-reference, so the id will be the creation id prefixed with a #.)
```
It needs to be an EmailSubmission id and the email id needs to be inferred from
the EmailSubmission.
https://github.com/apache/james-project/pull/356 fixes this syntax, by doing a
lookup within the current method call, find the submission, and takes the
associated emailId.
Because we do not have storage for email submission, references accross method
calls, and API requests will not be supported.
> [JMAP] Send: EmailSubmission/create (user email)
>
>
> Key: JAMES-3434
> URL: https://issues.apache.org/jira/browse/JAMES-3434
> Project: James Server
> Issue Type: Sub-task
>Reporter: René Cordier
>Priority: Major
> Fix For: 3.6.0
>
>
> h2. Why
> As a user, I want to send an existing email.
> h2. How
> Implement `EmailSubmission/set create`
> {code:json}
> [[ "EmailSubmission/set", {
> "accountId": "ue411d190",
> "create": {
> "k1490": {
> "emailId": "M7f6ed5bcfd7e2604d1753f6c",
> "envelope": {
> "mailFrom": {
> "email": "j...@example.com",
> "parameters": null
> },
>"rcptTo": [{
> "email": "j...@example.com",
> "parameters": null
>}]
> }
>}
> }
> }, "0" ]]
> {code}
> Note: IdentityId is not specified.
> Note: EmailParameters should be left null.
> Creating an EmailSubmission gets the given email being sent.
> Restrictions:
> * The FROM field of the envelope needs to belong to the sender. In which
> case it fails with `forbiddenMailFrom`.
> * The FROM field of the EML needs to belong to the sender. In which case it
> fails with `forbiddenFrom`.
> h2. Definition of Done
> Write a unit test demonstrating you can send emails.
>
--
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
[BUILD-FAILURE]: Job 'james/ApacheJames/master [master] [55]'
BUILD-FAILURE: Job 'james/ApacheJames/master [master] [55]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames/job/master/55/;>james/ApacheJames/master [master] [55]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313506#comment-17313506 ] ASF GitHub Bot commented on JAMES-3226: --- chibenwa commented on pull request #3: URL: https://github.com/apache/james-site/pull/3#issuecomment-812269829 ``` JDK 11 (latest)— Use a tool from a predefined Tool Installation<1s No hudson.model.JDK named JDK 11 (latest) found ``` -- 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
[jira] [Closed] (JAMES-3524) Re-enable AES encryption for the BlobStore
[ https://issues.apache.org/jira/browse/JAMES-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3524. - Fix Version/s: 3.6.0 Resolution: Fixed https://github.com/apache/james-project/pull/342 solved this > Re-enable AES encryption for the BlobStore > -- > > Key: JAMES-3524 > URL: https://issues.apache.org/jira/browse/JAMES-3524 > Project: James Server > Issue Type: Task > Components: Blob >Affects Versions: 3.6.0 >Reporter: Benoit Tellier >Priority: Major > Labels: security > Fix For: 3.6.0 > > Time Spent: 4.5h > Remaining Estimate: 0h > > Users might not wish to administrate themselves a S3 compatible blobStore and > might rely on a third arty to do so. As such, in order to avoid a third party > compromission to escalate to a data leak, a good practice is to encrypt the > data symmetrically, the secret key generation secrets being stored on the > appkication server. > Such a mechanism prevents data leak for a third party compromission, but do > not deend against an application server compromission (as the attacker would > then know the private key). > As part of his work on a Swift compatible blob store [1] , Jean Helou > contributed an AES encryption mechanism for that very blob store [2]. > However, changes in the blobStore design, dropping of the (non-reactive) > JCloud driver, rewrite on top of S3 API, as well as modularization of the > blobStore (extraction of the BlobStoreDAO, PassThough VS Deduplicating > blobStore) [3] lead to this work being dropped, for the sake of simplicity in > an effort to finish a long lasting refactoring. > Note that: > - Needs to encrypt blob payload had been requested on top of the Cassandra > blob store [4] in order to prevents (full) data leaks from a Cassandra DB > compromission. > - Some optimizations (prior [3]) of the object storage when using S3 were > incompatible with payload encryption [5] > By adoption design proposed in [3], reusing the job made by Jean in [2] we > can write a generic AESBlobStoreDAO that wraps any other BlobStoreDAO, adding > a security layer. Using the BlobStoreChooser, we then can re-enable this > capability on top of the Distributed James server. > [1] https://issues.apache.org/jira/browse/JAMES-2525 > [2] https://github.com/linagora/james-project/pull/1865 & > https://github.com/linagora/james-project/pull/1975 & > https://issues.apache.org/jira/browse/JAMES-2589 > [3] https://issues.apache.org/jira/browse/JAMES-3028 > [4] https://issues.apache.org/jira/browse/JAMES-3023 > [5] https://issues.apache.org/jira/browse/JAMES-2692 -- 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
[jira] [Closed] (JAMES-3525) Authentication required for same domain different user
[ https://issues.apache.org/jira/browse/JAMES-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3525. - Fix Version/s: 3.7.0 3.6.0 Resolution: Fixed https://github.com/apache/james-project/pull/349 solved this, merged on master, backported on 3.6.0 > Authentication required for same domain different user > -- > > Key: JAMES-3525 > URL: https://issues.apache.org/jira/browse/JAMES-3525 > Project: James Server > Issue Type: Improvement > Components: SMTPServer >Affects Versions: 3.5.0 >Reporter: Babu Raj K R >Priority: Major > Fix For: 3.6.0, 3.7.0 > > Attachments: mailetcontainer.xml, smtpserver.xml > > > I am using james-server-app-3.5.0-app. > We have a local domain mapped in our local dns server named syncme.com . > This mail server is used in our WAN only(no public ip). > We created 2 users- 1) [b...@syncme.com|mailto:b...@syncme.com] - 2) > [u...@syncme.com|mailto:u...@syncme.com] > We enabled auth in mail server. SMTP and POP works fine. > This problem is :- > I can send mail from [b...@syncme.com|mailto:b...@syncme.com] to > [u...@syncme.com|mailto:u...@syncme.com] without authentication > The above scenario i need to block and for all SMTP transmission i need > authentication. > What should i need to do this for enabling the above one. > -- 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
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [6]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [6]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/6/;>james/ApacheJames-Website/PR-3 [PR-3] [6]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]'
Hi all, Sorry about the spam, I opened a PR to try and improve the build flow for james documentation to try and get the staged documentation published automatically after each build of james project. Unfortunately the Jenkinsfile currently in the staging branch of james-site is out of date (the JDK name has changed) and It took me these 5 tries to realize that none of the changes I was making to the Jenkinsfile were accounted for because: ‘Jenkinsfile’ has been modified in an untrusted revision I'm not sure what the best way to proceed is : this limitation can be disabled (would be easiest since I may have further adjustments to make), or an official apache committer can push to an alternate PR to get it to build with the changes. Note that in this change I have also changed the email notifications to only notify the list for the live and staging branches and notify the requester for other branches. best regards jean On Thu, Apr 1, 2021 at 9:43 PM Apache Jenkins Server < jenk...@builds.apache.org> wrote: > BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]': > > Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/5/;>james/ApacheJames-Website/PR-3 > [PR-3] [5]" > > - > To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org > For additional commands, e-mail: server-dev-h...@james.apache.org
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [5]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/5/;>james/ApacheJames-Website/PR-3 [PR-3] [5]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [4]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [4]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/4/;>james/ApacheJames-Website/PR-3 [PR-3] [4]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [3]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [3]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/3/;>james/ApacheJames-Website/PR-3 [PR-3] [3]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [2]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [2]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/2/;>james/ApacheJames-Website/PR-3 [PR-3] [2]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313388#comment-17313388 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil opened a new pull request #3: URL: https://github.com/apache/james-site/pull/3 This enables building and publishing the antora documentation automatically when the build of the master branche of james-project is green. -- 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
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-3 [PR-3] [1]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-3 [PR-3] [1]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-3/1/;>james/ApacheJames-Website/PR-3 [PR-3] [1]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313387#comment-17313387 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil closed pull request #2: URL: https://github.com/apache/james-site/pull/2 -- 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
[BUILD-UNSTABLE]: Job 'james/ApacheJames-Website/PR-2 [PR-2] [1]'
BUILD-UNSTABLE: Job 'james/ApacheJames-Website/PR-2 [PR-2] [1]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames-Website/job/PR-2/1/;>james/ApacheJames-Website/PR-2 [PR-2] [1]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3226) Provide a process around documentation publishing and deployment
[ https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17313386#comment-17313386 ] ASF GitHub Bot commented on JAMES-3226: --- jeantil opened a new pull request #2: URL: https://github.com/apache/james-site/pull/2 -- 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
[BUILD-STABLE]: Job 'james/ApacheJames/master [master] [54]'
BUILD-STABLE: Job 'james/ApacheJames/master [master] [54]': Is back to normal. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
