You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@datasketches.apache.org by le...@apache.org on 2020/10/27 00:12:20 UTC

[incubator-datasketches-website] branch master updated: Updated.

This is an automated email from the ASF dual-hosted git repository.

leerho pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-datasketches-website.git


The following commit(s) were added to refs/heads/master by this push:
     new d04686b  Updated.
d04686b is described below

commit d04686bd1eb292921524344fef67a35806e832aa
Author: Lee Rhodes <le...@users.noreply.github.com>
AuthorDate: Mon Oct 26 17:12:01 2020 -0700

    Updated.
---
 docs/Maturity.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/docs/Maturity.md b/docs/Maturity.md
index 8b237fd..361432d 100644
--- a/docs/Maturity.md
+++ b/docs/Maturity.md
@@ -118,8 +118,9 @@ reliably used to validate the downloaded archives.
 > Convenience binaries can be distributed alongside source code but they are not 
 Apache Releases -- they are just a convenience provided with no guarantee.
 
-#### Yes.
-  * So far, we do not have any convenience binaries to distribute.
+#### Under Discussion
+  * We distribute Java jar file bundles via [Nexus Repository Manager](https://repository.apache.org). These jar files include source jars as well as compiled binaries of the source code. 
+  * 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.
 
 ### RE50
 > The release process is documented and repeatable to the extent that
@@ -161,7 +162,7 @@ incompatible changes and provide tools and documentation to help users transitio
 #### Yes.
   * We define two types of backward compatibility, API, and Binary:
      * **API:** 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.
-     * **Binary:** 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.
+     * **Binary:** 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.
 
 ### QU50
 > The project strives to respond to documented bug reports in a timely manner.


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datasketches.apache.org
For additional commands, e-mail: commits-help@datasketches.apache.org