This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/james-site.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 1aa9503 Site checkin for project Apache James: Jenkins Tools
1aa9503 is described below
commit 1aa9503c6c1b6ae72fb0373044902378bca6a9ec
Author: jenkins <bui...@apache.org>
AuthorDate: Fri Jan 28 10:32:58 2022 +0000
Site checkin for project Apache James: Jenkins Tools
---
james-project/3.7.0/community/contributing.html | 125 ++++++++++----------
james-project/3.7.0/community/guidelines.html | 147 ++++++++++++++++--------
sitemap-james-project.xml | 92 +++++++--------
sitemap-james-site.xml | 4 +-
4 files changed, 206 insertions(+), 162 deletions(-)
diff --git a/james-project/3.7.0/community/contributing.html
b/james-project/3.7.0/community/contributing.html
index efc2322..9a95a8e 100644
--- a/james-project/3.7.0/community/contributing.html
+++ b/james-project/3.7.0/community/contributing.html
@@ -388,14 +388,11 @@
<li>
<p><a href="https://issues.apache.org/jira/browse/JDKIM";>jDKIM</a></p>
</li>
-<li>
-<p><a href="https://issues.apache.org/jira/browse/HUPA";>Hupa</a></p>
-</li>
</ul>
</div>
<div class="paragraph">
<p>Once you are logged on the appropriate JIRA page, click on the red Create
button, then complete the different fields
-as accurately as possible, so that any user can reproduce the reported bug.
Also note that all your information must be
+as accurately as possible, so that any user can reproduce the reported bug.
Also, note that all your information must be
readable (use markdown).</p>
</div>
<div class="paragraph">
@@ -441,8 +438,46 @@ which will be automatically published via gitpubsub to <a
href="http://james.apa
</div>
</div>
<div class="sect1">
+<h2 id="_idea_or_design_proposals"><a class="anchor"
href="#_idea_or_design_proposals"></a>Idea or design proposals</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>People can submit ideas, features or design changes proposals by discussing
it through the
+<a href="mailing-lists.html" class="page">mailing lists</a>.</p>
+</div>
+<div class="paragraph">
+<p>Structuring design changes are tracked by <a
href="https://github.com/joelparkerhenderson/architecture-decision-record";>ADRs</a>
+(Architecture Decision Records). A discussion on the mailing list getting a
consensus of the community can be the object
+of the writing of an ADR to confirm the change agreed upon. The Project Member
Committee will take care of maintaining such
+records but anyone should feel free to help on such a task by proposing ADRs
related to his work.</p>
+</div>
+<div class="paragraph">
+<p>ADRs <strong>MUST</strong> be submitted under the folder
<code>src/adr</code> via a pull request. The standards used for writing an ADR
are
+described in the <a
href="https://github.com/apache/james-project/blob/master/src/adr/0001-record-architecture-decisions.md";>first
ADR</a>
+written for the Apache James project.</p>
+</div>
+<div class="paragraph">
+<p>The number of the ADR should be incremental. If another ADR gets merged
concurrently, the committer is responsible for
+updating its number accordingly.</p>
+</div>
+<div class="paragraph">
+<p>When the ADR reaches a consensus within the community and is accepted, it
can be merged and goes into effect.</p>
+</div>
+<div class="paragraph">
+<p>An ADR can’t be removed after being accepted and merged. However, a
new ADR can supersede a previous one. This is so
+we are able to keep track on all the decisions being made regarding the
project.</p>
+</div>
+</div>
+</div>
+<div class="sect1">
<h2 id="_how_to_contribute_some_code"><a class="anchor"
href="#_how_to_contribute_some_code"></a>How to contribute some code?</h2>
<div class="sectionbody">
+<div class="paragraph">
+<p>We encourage discussions prior code contributions on the <a
href="mailing-lists.html" class="page">mailing lists</a>. For significant design
+changes the writing of <a href="#_idea_or_design_proposals">ADRs</a> is
encouraged.</p>
+</div>
+<div class="paragraph">
+<p>Your code contribution <strong>must</strong> be backed by a <a
href="#_reporting_bugs">JIRA ticket</a>.</p>
+</div>
<div class="ulist">
<ul>
<li>
@@ -453,14 +488,17 @@ which will be automatically published via gitpubsub to <a
href="http://james.apa
<p>Create your branch and name it with the JIRA ticket number.</p>
</li>
<li>
-<p>Create a Pull Request with your branch name and prefix its different
commits with the same name.</p>
+<p>Create a Pull Request on Github with your branch name and prefix its
different commits with the same name.</p>
+</li>
+<li>
+<p>A build will be started for your work on the <a
href="https://ci-builds.apache.org/job/james/job/ApacheJames/";>Apache
CI</a>.</p>
+</li>
+<li>
+<p>Active contributors will review your work, and merge it.</p>
</li>
</ul>
</div>
<div class="paragraph">
-<p>Alternatively you can create a patch as <a href="#_code_patches">outlined
below</a>, and attach it to the JIRA ticket.</p>
-</div>
-<div class="paragraph">
<p>A valid commit comment might be:</p>
</div>
<div class="listingblock">
@@ -470,6 +508,9 @@ which will be automatically published via gitpubsub to <a
href="http://james.apa
Here is some more details about what my commit does, and the rationals of the
choice I took.</code></pre>
</div>
</div>
+<div class="paragraph">
+<p>Alternatively you can create a patch as <a href="#_code_patches">outlined
below</a>, and attach it to the JIRA ticket.</p>
+</div>
<div class="sect2">
<h3 id="_licenses"><a class="anchor" href="#_licenses"></a>Licenses</h3>
<div class="paragraph">
@@ -505,35 +546,15 @@ Here is some more details about what my commit does, and
the rationals of the ch
than none, please consider these guidelines to help us to assimilate your
contribution.</p>
</div>
<div class="paragraph">
-<p>Submissions to the James project must follow the coding conventions
outlined in this document. James developers are
-asked to follow coding conventions already present in the code. (For example,
if the existing code has the bracket on
-the same line as the if statement, then all subsequent code should also follow
that convention.) Anything not explicitly
-mentioned in this document should adhere to the official
-<a
href="https://www.oracle.com/java/technologies/javase/codeconventions-contents.html";>Java
Coding Conventions</a>.</p>
+<p>Submissions to the James project must follow the coding conventions
outlined in the
+<a
href="https://github.com/apache/james-project/blob/master/checkstyle.xml";>checkstyle
document</a>, which runs
+upon <code>mvn compile</code> and all phases which depend on
<code>compile</code>. Not respecting it will halt the build, and means
+your contribution would not be
+acceptable.</p>
</div>
<div class="paragraph">
<p><strong>Developers who commit code that does not follow the coding
conventions outlined in this document will be responsible
-for fixing their own code.</strong></p>
-</div>
-<div class="olist arabic">
-<ol class="arabic">
-<li>
-<p>Your code should pass our <a
href="https://github.com/apache/james-project/blob/master/checkstyle.xml";>checkstyle</a>
which runs
-upon <code>mvn compile</code> and all phases which depend on
<code>compile</code>.</p>
-</li>
-<li>
-<p>Extra spaces between parentheses are not allowed:</p>
-</li>
-</ol>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="highlightjs highlight"><code> if (foo) > Good
-
- or
-
- if ( foo ) > Bad</code></pre>
-</div>
+for fixing their own code.</strong> `.</p>
</div>
<div class="olist arabic">
<ol class="arabic" start="3">
@@ -560,8 +581,8 @@ GREATLY appreciated as this will help to improve the James
project.</p>
<div class="ulist">
<ul>
<li>
-<p>Define your dependency versions in james-project pom.xml. This structurally
ensures all projects get the same v
-ersion, and that there is no version clashes.</p>
+<p>Define your dependency versions in james-project pom.xml. This structurally
ensures all projects get the same version,
+and that there is no version clashes.</p>
</li>
<li>
<p>Don’t use <em>org.apache.james</em> groupId for internal
dependencies. Use <em>${james.groupId}</em>. If not, you break the policies
@@ -601,6 +622,11 @@ sometimes remove whitespaces which may not be
desirable.</p>
<div class="sect2">
<h3 id="_code_patches"><a class="anchor" href="#_code_patches"></a>Code
patches</h3>
<div class="paragraph">
+<p>While we definitely prefer receiving contributions under the form of <a
href="#_how_to_contribute_some_code">Github pull requests</a>,
+in order to still be vendor neutral on the contribution process, we do accept
submission of patches, in a process described
+below.</p>
+</div>
+<div class="paragraph">
<p>Patches should be attached to the corresponding JIRA issue.</p>
</div>
<div class="paragraph">
@@ -625,33 +651,6 @@ patch is more likely to be committed quickly.</p>
</div>
</div>
</div>
-<div class="sect1">
-<h2 id="_idea_or_design_proposals"><a class="anchor"
href="#_idea_or_design_proposals"></a>Idea or design proposals</h2>
-<div class="sectionbody">
-<div class="paragraph">
-<p>People can submit ideas, features or design changes proposals by discussing
it through the
-<a href="mailing-lists.html" class="page">mailing lists</a> and/or submitting
an ADR (Architecture Decision Record). A discussion
-on the mailing list getting a consensus of the community can be the object of
the writing of an ADR to confirm the
-change agreed upon.</p>
-</div>
-<div class="paragraph">
-<p>ADRs <strong>MUST</strong> be submitted under the folder
<code>src/adr</code> via a pull request. The standards used for writing an ADR
are
-described in the <a
href="https://github.com/apache/james-project/blob/master/src/adr/0001-record-architecture-decisions.md";>first
ADR</a>
-written for the Apache James project.</p>
-</div>
-<div class="paragraph">
-<p>The number of the ADR should be incremental. If an other ADR gets merged
concurrently, the committer is responsible for
-updating its number accordingly.</p>
-</div>
-<div class="paragraph">
-<p>When the ADR reaches a consensus within the community and is accepted, it
can be merged and goes into effect.</p>
-</div>
-<div class="paragraph">
-<p>An ADR can’t be removed after being accepted and merged. However, a
new ADR can supersede a previous one. This is so
-we are able to keep track on all the decisions being made regarding the
project.</p>
-</div>
-</div>
-</div>
</article>
</div>
</main>
diff --git a/james-project/3.7.0/community/guidelines.html
b/james-project/3.7.0/community/guidelines.html
index c92a3d2..9db619c 100644
--- a/james-project/3.7.0/community/guidelines.html
+++ b/james-project/3.7.0/community/guidelines.html
@@ -384,6 +384,27 @@ only subscribers can post directly to the list.</p>
such as legal, personal, or security issues prior to a published fix.
Subscription to the list is only opened to Apache
James PMC members and Apache Software Foundation Members.</p>
</div>
+<div class="paragraph">
+<p>Topics to be discussed on the private mailing list:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Discussion of board reports. PMC members need to report quaterly project
activity to the Apache board of directors,
+which is done through <a
href="https://reporter.apache.org";>reporter.apache.org</a>. Prior report
submission, the draft should
+be discussed on the private mailing list.</p>
+</li>
+<li>
+<p>Discussions of <a href="https://community.apache.org/newcommitter.html";>new
committers, new PMCs</a>, including proposition discussions, votes and process
follow up.</p>
+</li>
+<li>
+<p>Handling of <a href="contributing.html#_reporting_security_vulnerabilities"
class="page">security vulnerability reports</a>, and CVE publication.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Other topics should be discussed/voted on server-dev instead.</p>
+</div>
</div>
<div class="sect2">
<h3 id="_git"><a class="anchor" href="#_git"></a>GIT</h3>
@@ -395,13 +416,49 @@ The Apache committers have write access to these
repositories; everyone has read
</div>
</div>
<div class="sect1">
-<h2 id="_voting"><a class="anchor" href="#_voting"></a>Voting</h2>
+<h2 id="_consensus"><a class="anchor" href="#_consensus"></a>Consensus</h2>
<div class="sectionbody">
<div class="paragraph">
+<p>As a community we are seeking <a
href="https://community.apache.org/committers/decisionMaking.html";>consensus</a>
in our
+decision making.</p>
+</div>
+<div class="paragraph">
+<p>We actively rely on <a
href="https://community.apache.org/committers/lazyConsensus.html";>lazy
consensus</a> for most of our
+decisions, be them validating <a
href="contributing.html#_how_to_contribute_some_code" class="page">code
changes</a>, enacting
+<a href="contributing.html#_idea_or_design_proposals" class="page">design
decisions</a>.</p>
+</div>
+<div class="paragraph">
+<p>All code modifications should achieve lazy consensus under the form of
github pull requests.</p>
+</div>
+<div class="sect2">
+<h3 id="_voting"><a class="anchor" href="#_voting"></a>Voting</h3>
+<div class="paragraph">
+<p>Some decisions might require to vote:</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p><a href="release.html" class="page">releases</a></p>
+</li>
+<li>
+<p>establishing a new sub-project</p>
+</li>
+<li>
+<p>retiring sub-projects</p>
+</li>
+<li>
+<p>taking a decision when lazy consensus failed.</p>
+</li>
+</ul>
+</div>
+<div class="paragraph">
+<p>Note that we encourage discussing the issues prior to trigger a vote. That
way bad surprises may be avoided ahead of time.</p>
+</div>
+<div class="paragraph">
<p>Any of the Apache James Committers may vote on any issue or action item.
However, the only binding votes are those cast
by active members of the Apache James PMC; if the vote is about a change to
source code or documentation, the primary
author of what is being changed may also cast a binding vote on that issue.
All other votes are non-binding. All
-committers are encouraged to participate in decisions, but the decision itself
is made by those who have been long-time
+contributors are encouraged to participate in decisions, but the decision
itself is made by those who have been long-time
contributors to the project. In other words, the Apache Project is a
minimum-threshold meritocracy.</p>
</div>
<div class="paragraph">
@@ -446,74 +503,62 @@ send this to the mailing list. A developer should be
sensitive to holidays that
</div>
</div>
</div>
+</div>
<div class="sect1">
-<h2 id="_types_of_action_items"><a class="anchor"
href="#_types_of_action_items"></a>Types of Action Items</h2>
+<h2 id="_section_for_new_committers"><a class="anchor"
href="#_section_for_new_committers"></a>Section for new committers</h2>
<div class="sectionbody">
-<div class="sect2">
-<h3 id="_long_term_plans"><a class="anchor" href="#_long_term_plans"></a>Long
Term Plans</h3>
-<div class="paragraph">
-<p>Long term plans are simply announcements that group members are working on
particular issues related to the Apache
-software. These are not voted on, but group members who do not agree with a
particular plan, or think an alternate plan
-would be better, are obligated to inform the group of their feelings. In
general, it is always better to hear about
-alternate plans prior to spending time on less adequate solutions.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_short_term_plans"><a class="anchor"
href="#_short_term_plans"></a>Short Term Plans</h3>
<div class="paragraph">
-<p>Short term plans are announcements that a developer is working on a
particular set of documentation or code files, with
-the implication that other committers should avoid them or try to coordinate
their changes. This is a good way to
-proactively avoid conflict and possible duplication of work.</p>
-</div>
+<p>First congratulation for your involvement!</p>
</div>
-<div class="sect2">
-<h3 id="_release_plan"><a class="anchor" href="#_release_plan"></a>Release
Plan</h3>
<div class="paragraph">
-<p>A release plan is used to keep all the committers aware of when a release
is desired, who will be the release manager,
-when the repository will be frozen in order to create the release, and
assorted other trivia to keep us from tripping
-over ourselves during the final moments. Lazy majority decides each issue in
the release plan.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_release_testing"><a class="anchor"
href="#_release_testing"></a>Release Testing</h3>
-<div class="paragraph">
-<p>After a new release is built, colloquially termed a tarball, it must be
tested before being released to the public.
-Majority approval is required before the tarball can be publically
released.</p>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_showstoppers"><a class="anchor"
href="#_showstoppers"></a>Showstoppers</h3>
-<div class="paragraph">
-<p>Showstoppers are issues that require a fix be in place before the next
public release.</p>
+<p>As part of the <a
href="https://community.apache.org/newcommitter.html";>process to become a
committer</a>, the following steps should have had been emailed to you:</p>
</div>
+<div class="ulist">
+<ul>
+<li>
+<p>Signing of <a href="https://www.apache.org/licenses/#clas";>Contributor
License Agreement</a></p>
+</li>
+<li>
+<p>Establishing an Apache profile with the Apache secretary.</p>
+</li>
+<li>
+<p>Access will directly be granted on the <a
href="https://issues.apache.org/jira/projects/JAMES";>JIRA</a>,
+the ASF Git repository and the <a
href="https://ci-builds.apache.org/job/james/job/ApacheJames/";>ci</a>.</p>
+</li>
+<li>
+<p>Extra steps should be taken for <a
href="#_accessing_apache_github_as_a_committer">Github access</a>.</p>
+</li>
+<li>
+<p>A PMC should have had announced your nomination. If you have not already
been doing it, we strongly
+encourage you to write an email on public mailing list, presenting you, and
your motivations toward
+contributing on Apache James. A reply to the announce would do the trick!</p>
+</li>
+</ul>
</div>
<div class="sect2">
-<h3 id="_product_changes"><a class="anchor"
href="#_product_changes"></a>Product Changes</h3>
-<div class="paragraph">
-<p>Changes to the Apache James products, including code and documentation,
will appear as action items under several
-categories corresponding to the change status:</p>
-</div>
+<h3 id="_accessing_apache_github_as_a_committer"><a class="anchor"
href="#_accessing_apache_github_as_a_committer"></a>Accessing Apache GitHub as
a Committer</h3>
<div class="ulist">
<ul>
<li>
-<p><strong>Concept/Plan</strong>
-An idea or plan for a change. These are represented as ADRs (Architectural
Decision Records), stored under the <code>src/adr</code>
-folder. Votes are being requested early so as to uncover conflicts before too
much work is done. You can find more
-information about this <a href="contributing.html#_idea_or_design_proposals"
class="page">here</a>.</p>
+<p>Verify you have a Github ID enabled with <a
href="https://help.github.com/articles/securing-your-account-with-two-factor-authentication-2fa/";>2FA</a></p>
</li>
<li>
-<p><strong>Proposed Patch</strong>
-A specific set of changes to the current product in the form of input to the
patch command (a diff output).</p>
+<p>Enter your Github ID into your <a href="https://id.apache.org/";>Apache ID
profile</a></p>
</li>
<li>
-<p><strong>Committed Change</strong>
-A one-line summary of a change that has been committed to the repository since
the last public release.</p>
+<p>Merge your Apache and GitHub accounts using <a
href="https://gitbox.apache.org/setup/";>GitBox</a> (Apache Account Linking
utility). You should see 3 green checks in GitBox.</p>
</li>
</ul>
</div>
<div class="paragraph">
-<p>All product changes to the currently active repository are subject to lazy
consensus. All product changes to a
-prior-branch (old version) repository require consensus before the change is
committed.</p>
+<p>Wait at least 30 minutes for an email inviting you to Apache GitHub
Organization and accept invitation.</p>
+</div>
+<div class="ulist">
+<ul>
+<li>
+<p>After accepting the Github Invitation verify that you are a member of the
<a href="https://github.com/orgs/apache/teams/james-committers";>GitHub Apache
James team</a>.</p>
+</li>
+</ul>
</div>
</div>
</div>
diff --git a/sitemap-james-project.xml b/sitemap-james-project.xml
index 44c0d53..bbd2c57 100644
--- a/sitemap-james-project.xml
+++ b/sitemap-james-project.xml
@@ -2,186 +2,186 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/contributing.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/download.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/guidelines.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/mailing-lists.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/release.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/support.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/community/website.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/configuration.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/glossary.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/mail/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/messages/imf.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/messages/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/messages/mime.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/processing/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/protocols/esmtp.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/protocols/imap.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/protocols/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/protocols/jmap.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/protocols/lmtp.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/protocols/pop.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/protocols/smtp.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/storage/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/storage/mailbox.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/storage/users.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/concepts/user/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/customization/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/development/deployment-tests.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/development/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/development/logging.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/15-minute-demo.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/5-minute-demo.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/basic/architecture.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/basic/concepts.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/basic/conf/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/basic/context.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/basic/help.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/basic/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/basic/objectives.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/demo.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/extendable.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/run.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-project/3.7.0/servers/test.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
</urlset>
diff --git a/sitemap-james-site.xml b/sitemap-james-site.xml
index 8e0acb2..a246af9 100644
--- a/sitemap-james-site.xml
+++ b/sitemap-james-site.xml
@@ -2,10 +2,10 @@
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";>
<url>
<loc>https://james.apache.org/james-site/latest/homepage.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
<url>
<loc>https://james.apache.org/james-site/latest/index.html</loc>
-<lastmod>2022-01-27T10:48:50.816Z</lastmod>
+<lastmod>2022-01-28T10:31:14.869Z</lastmod>
</url>
</urlset>
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@james.apache.org
For additional commands, e-mail: notifications-h...@james.apache.org
