This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository
https://gitbox.apache.org/repos/asf/incubator-datasketches-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new fff418a Automatic Site Publish by Buildbot
fff418a is described below
commit fff418a3df8c568fc3939e5aab7a498d044dd40b
Author: buildbot <[email protected]>
AuthorDate: Tue Oct 27 00:12:39 2020 +0000
Automatic Site Publish by Buildbot
---
output/docs/Maturity.html | 47 ++++++++++++++++++++++++-----------------------
1 file changed, 24 insertions(+), 23 deletions(-)
diff --git a/output/docs/Maturity.html b/output/docs/Maturity.html
index cb53db6..f4b75d9 100644
--- a/output/docs/Maturity.html
+++ b/output/docs/Maturity.html
@@ -652,9 +652,10 @@ reliably used to validate the downloaded archives.</p>
Apache Releases – they are just a convenience provided with no guarantee.</p>
</blockquote>
-<h4 id="yes-12">Yes.</h4>
+<h4 id="under-discussion">Under Discussion</h4>
<ul>
- <li>So far, we do not have any convenience binaries to distribute.</li>
+ <li>We distribute Java jar file bundles via <a
href="https://repository.apache.org">Nexus Repository Manager</a>. These jar
files include source jars as well as compiled binaries of the source code.</li>
+ <li>We may have needs in the near future for distributions through other
venues, e.g., pgxn.org, pypi, and docker; some of these may be binaries, we are
not sure yet. We will consult with Infra and others to make sure we are doing
it right.</li>
</ul>
<h3 id="re50">RE50</h3>
@@ -664,7 +665,7 @@ someone new to the project is able to independently
generate the complete
set of artifacts required for a release.</p>
</blockquote>
-<h4 id="yes-13">Yes.</h4>
+<h4 id="yes-12">Yes.</h4>
<ul>
<li>All committers have access to <a
href="https://dist.apache.org/repos/dist/dev/incubator/datasketches/scripts/">detailed
release scripts</a>.</li>
<li>As of October 24, 2020, we have successfully completed 17 Apache
releases since the start of our incubation.</li>
@@ -679,7 +680,7 @@ of quality and maturity for various modules are natural and
acceptable
as long as they are clearly communicated.</p>
</blockquote>
-<h4 id="yes-14">Yes.</h4>
+<h4 id="yes-13">Yes.</h4>
<ul>
<li>Bugs, various deficiencies and documentation problems come to us from
many different sources. Once these bugs are made known to us we record them
using the GitHub issues lists of the relevant repository<sup>1</sup>.</li>
</ul>
@@ -689,7 +690,7 @@ as long as they are clearly communicated.</p>
<p>The project puts a very high priority on producing secure software.</p>
</blockquote>
-<h3 id="yes-15">Yes.</h3>
+<h3 id="yes-14">Yes.</h3>
<ul>
<li>Security issues will be treated with the highest priority.</li>
<li>We will follow the guidelines proposed by <a
href="https://cve.mitre.org/about/documents.html">CVE Documents and
Guidance</a> should these issues arise.</li>
@@ -700,7 +701,7 @@ as long as they are clearly communicated.</p>
<p>The project provides a well-documented, secure and private channel to
report security issues, along with a documented way of responding to them.</p>
</blockquote>
-<h4 id="yes-16">Yes.</h4>
+<h4 id="yes-15">Yes.</h4>
<ul>
<li>See <a
href="https://datasketches.apache.org/docs/Community/index.html">Community
page, “Reporting Security Issues”</a>.</li>
</ul>
@@ -711,12 +712,12 @@ as long as they are clearly communicated.</p>
incompatible changes and provide tools and documentation to help users
transition to new features.</p>
</blockquote>
-<h4 id="yes-17">Yes.</h4>
+<h4 id="yes-16">Yes.</h4>
<ul>
<li>We define two types of backward compatibility, API, and Binary:
<ul>
<li><strong>API:</strong> To the greatest extent possible we try to
maintain compatiblity with older APIs. However, some API changes are
inevitable. In these cases we deprecate the older API alongside the newer
recommended API for at least one major release cycle, after which the older API
may be removed. This is standard policy for most industry code bases.</li>
- <li><strong>Binary:</strong> Our current codebase is able to read and
process older binary representations of our sketches since about 2014. This is
extremely important for our customers and is very high priority as our code
evolves.</li>
+ <li><strong>Binary:</strong> Our current codebase is able to read and
process older binary representations of our sketches since about 2014. This is
extremely important for our users and is very high priority as our code
evolves.</li>
</ul>
</li>
</ul>
@@ -726,7 +727,7 @@ incompatible changes and provide tools and documentation to
help users transitio
<p>The project strives to respond to documented bug reports in a timely
manner.</p>
</blockquote>
-<h4 id="yes-18">Yes.</h4>
+<h4 id="yes-17">Yes.</h4>
<ul>
<li>We respond very quickly to bug and problem reports and have received
excellent feedback from our users about our quick response.</li>
</ul>
@@ -739,7 +740,7 @@ incompatible changes and provide tools and documentation to
help users transitio
required to operate according to this maturity model.</p>
</blockquote>
-<h4 id="yes-19">Yes.</h4>
+<h4 id="yes-18">Yes.</h4>
<ul>
<li>See <a
href="https://datasketches.apache.org">datasketches.apache.org</a>.</li>
</ul>
@@ -750,7 +751,7 @@ required to operate according to this maturity model.</p>
faith and in a respectful manner and adds value to the project.</p>
</blockquote>
-<h4 id="yes-20">Yes.</h4>
+<h4 id="yes-19">Yes.</h4>
<ul>
<li>See <a
href="https://datasketches.apache.org/docs/Community/index.html">Community,
Contributing topic</a>.</li>
</ul>
@@ -761,7 +762,7 @@ faith and in a respectful manner and adds value to the
project.</p>
reports, constructive discussions, marketing and generally anything that adds
value to the project.</p>
</blockquote>
-<h4 id="yes-21">Yes.</h4>
+<h4 id="yes-20">Yes.</h4>
<ul>
<li>See <a
href="https://datasketches.apache.org/docs/Community/index.html">Community,
Contributing topic</a>.</li>
</ul>
@@ -772,7 +773,7 @@ reports, constructive discussions, marketing and generally
anything that adds va
responsibilities to contributors who add value to the project.</p>
</blockquote>
-<h4 id="yes-22">Yes.</h4>
+<h4 id="yes-21">Yes.</h4>
<ul>
<li>We have elected one new committer and have more on the way. All of these
are and will be meritocracy based.</li>
</ul>
@@ -783,7 +784,7 @@ responsibilities to contributors who add value to the
project.</p>
access or decision power is clearly documented and is the same for all
contributors.</p>
</blockquote>
-<h4 id="yes-23">Yes.</h4>
+<h4 id="yes-22">Yes.</h4>
<ul>
<li>See <a
href="https://datasketches.apache.org/docs/Community/index.html">Community,
Contributing topic</a>.</li>
</ul>
@@ -795,7 +796,7 @@ have decision power. Dictators, benevolent or not, are not
welcome in
Apache projects.</p>
</blockquote>
-<h4 id="yes-24">Yes.</h4>
+<h4 id="yes-23">Yes.</h4>
<ul>
<li>We work hard to build consensus.</li>
</ul>
@@ -805,7 +806,7 @@ Apache projects.</p>
<p>The project strives to answer user questions in a timely manner.</p>
</blockquote>
-<h4 id="yes-25">Yes.</h4>
+<h4 id="yes-24">Yes.</h4>
<ul>
<li>We typically respond to issues within a few hours. These issues come to
our attention through many different channels including our
[email protected], [email protected], and GitHub issues
lists as well as the Apache Slack channels.</li>
</ul>
@@ -818,7 +819,7 @@ power – the project’s PMC (Project Management Committee)
consists of
those contributors.</p>
</blockquote>
-<h4 id="yes-26">Yes.</h4>
+<h4 id="yes-25">Yes.</h4>
<ul>
<li>See <a
href="https://incubator.apache.org/projects/datasketches.html">DataSketches
Project Incubation Status</a>.</li>
</ul>
@@ -830,7 +831,7 @@ and are documented on the project’s main communications
channel.
Community opinions are taken into account but the PMC has the final word, if
needed.</p>
</blockquote>
-<h4 id="yes-27">Yes.</h4>
+<h4 id="yes-26">Yes.</h4>
<ul>
<li>All major projecct decisions are documented via our <a
href="mailto:[email protected]">[email protected]</a>
mail list.</li>
</ul>
@@ -840,7 +841,7 @@ Community opinions are taken into account but the PMC has
the final word, if nee
<p>Documented voting rules are used to build consensus when discussion is
not sufficient.</p>
</blockquote>
-<h4 id="yes-28">Yes.</h4>
+<h4 id="yes-27">Yes.</h4>
<ul>
<li>The project uses the standard ASF voting rules. Voting rules are clearly
stated before the voting starts for each individual vote.</li>
</ul>
@@ -852,7 +853,7 @@ justified by a technical explanation, as per the Apache
voting rules
defined in CS30.</p>
</blockquote>
-<h4 id="yes-29">Yes.</h4>
+<h4 id="yes-28">Yes.</h4>
<ul>
<li>We have had only one instance of a “-1” vote from a PPMC member on a
code release. The issue was fixed and resubmitted. We support this policy.</li>
</ul>
@@ -864,7 +865,7 @@ project’s main communications channel. Offline,
face-to-face or private discus
that affect the project are also documented on that channel.</p>
</blockquote>
-<h4 id="yes-30">Yes.</h4>
+<h4 id="yes-29">Yes.</h4>
<ul>
<li>The project has been making important decisions on the project mailing
lists. Minor decisions may occasionally happen during code reviews, which are
also asynchronous and in written form. Any synchronous discussions that result
in major decisions for the project are documented oun our project <a
href="mailto:[email protected]">[email protected]</a>
mailing list.</li>
</ul>
@@ -876,7 +877,7 @@ that affect the project are also documented on that
channel.</p>
<p>The project is independent from any corporate or organizational
influence.</p>
</blockquote>
-<h4 id="yes-31">Yes.</h4>
+<h4 id="yes-30">Yes.</h4>
<ul>
<li>Our project has committers and contributors from Verizon Media, Inc.;
Hypercube, Inc.; Permutive, Inc. UK;
Tableau (Salesforce, Inc.); Georgetown University, Washington, D.C.; Warwick
University, UK;
@@ -888,7 +889,7 @@ UC Berkeley; Apache Druid, and other researchers from
around the world.</li>
<p>Contributors act as themselves as opposed to representatives of a
corporation or organization.</p>
</blockquote>
-<h4 id="yes-32">Yes.</h4>
+<h4 id="yes-31">Yes.</h4>
<ul>
<li>The committers and contributors act on their own initiative without
representing a corporation or organization.</li>
</ul>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]