[ANNOUNCE] Apache Pulsar 2.10.0 released

2022-04-19 Thread PengHui Li
The Apache Pulsar team is proud to announce Apache Pulsar version 2.10.0.

Pulsar is a highly scalable, low latency messaging platform running on
commodity hardware. It provides simple pub-sub semantics over topics,
guaranteed at-least-once delivery of messages, it also provides transaction
feature since 2.8.0, guaranteed exactly-once semantics for producing and
consuming process over topics, automatic cursor management for
subscribers, and cross-datacenter replication.

For Pulsar release details and downloads, visit:

https://pulsar.apache.org/download

Release Notes are at:
https://pulsar.apache.org/release-notes/#2100

We would like to thank the contributors that made the release possible.

Regards,

The Pulsar Team


[ANNOUNCE] Apache CouchDB 3.2.2 released

2022-04-19 Thread Jan Lehnardt
Dear community,

Apache CouchDB® 3.2.2 has been released and is available for download.

Apache CouchDB® lets you access your data where you need it. The Couch 
Replication Protocol is implemented in a variety of projects and products that 
span every imaginable computing environment from globally distributed 
server-clusters, over mobile phones to web browsers.

Store your data safely, on your own servers, or with any leading cloud 
provider. Your web- and native applications love CouchDB, because it speaks 
JSON natively and supports binary data for all your data storage needs.

The Couch Replication Protocol lets your data flow seamlessly between server 
clusters to mobile phones and web browsers, enabling a compelling offline-first 
user-experience while maintaining high performance and strong reliability. 
CouchDB comes with a developer-friendly query language, and optionally 
MapReduce for simple, efficient, and comprehensive data retrieval.

https://couchdb.apache.org/#download

Pre-built packages for Windows, macOS, Debian/Ubuntu and RHEL/CentOS are 
available.

CouchDB 3.2.2 is a maintenance release, and was originally published on 
2022-04-19.

The community would like to thank all contributors for their part in making 
this release, from the smallest bug report or patch to major contributions in 
code, design, or marketing, we couldn’t have done it without you!

See the official release notes document for an exhaustive list of all changes:

http://docs.couchdb.org/en/stable/whatsnew/3.2.html

Release Notes highlights:

  - This releases includes a fix for CVE-2022-24706, the nature of which will 
be announced a week after the release.

  - Optimize compaction and doc updates for conflicted documents on Erlang 
versions higher than 21.

  - Add support for SpiderMonkey 91esr.

On behalf of the CouchDB PMC,
Jan Lehnardt
—

[ANNOUNCE] Apache Teaclave (incubating) 0.4.0 released

2022-04-19 Thread Mingshen Sun
Dear community,

The Apache Teaclave (incubating) team is pleased to announce the
release of Apache Teaclave (incubating) 0.4.0.

Apache Teaclave (incubating) is an open source universal secure
computing platform, making computation on privacy-sensitive data safe
and simple.

This is the fourth official Apache incubator release. In this release,
we mainly focus on better user management, task management,
performance improvement and stability.

In this release, we introduce a role-based access control for user
management.  Specifically, we define roles like admin, function owner,
data owner, data owner manager, etc. Additionally, we also add APIs to
support user management functionalities.  In addition, we also
implement a feature to cancel a running task to kill a long-run
function which is no longer needed. Besides these two new features, we
also made a lot of underlying changes to improve the performance of
RPC and stability of the secure database.

To learn more, here is a list of notable changes in Teaclave version 0.4.0.

**Features**

- Add the `DisableFunction` interface (#620)
- Better user management interfaces: add the `UserUpdate`,
`UserChangePassword`, `ResetUserPassword`, `DeleteUser`, and
`ListUsers` interfaces
- Support optional input/output files (#603)
- Start Teaclave docker services with auto-detection mechanism (#559)
- Add watchdog functionality to monitor service status (#600)
- Support cancel a task
- Support intermediate cert in DCAP attestation cert

**Enhancements**

- Better error handling in Python client SDK (#632)
- Refactor services error types and messages, make them readable to end users
- Optimize RPC memory footprint of serde (#577)
- Support selectively including executors (#574)
- Support AES-GCM output files (#629)
- Add port probe for service launching
- Update WAMR version to WAMR-01-18-2022 (#616)
- Move execution context into a separate crate (#598)
- Support Ubuntu 20.04 docker image and add corresponding CI pipelines
- Persistent MockDB in test mode (#580)

**Bug Fixes**

- Better task state error and fix cancel error issue in the example (#637)
- Fix privilege issues in the `GetFunction` and `ListFunctions`
interfaces (#636)
- Better building system: fix packages rebuild every time, avoid
issues in parallel make (#589, #596)
- Fix the issue of generating code coverage of tests (#627)
- Fix LevelDB assertion issue: leveldb lru bug, using disk db for unit
test (#583)

**Docs**

- Add release guide for releasing Teaclave in the community:

- Remove `CONTRIBUTORS.md` and point to the homepage (#552)

Release notes can be found here:
https://github.com/apache/incubator-teaclave/releases/tag/v0.4.0

A link to the download can be found here: https://teaclave.apache.org/download/

To learn more about Teaclave, please visit: https://teaclave.apache.org/


Best,
Mingshen Sun
The Apache Teaclave (incubating) Team

===

*Disclaimer*

Apache Teaclave (incubating) is an effort undergoing incubation at The
Apache Software Foundation (ASF), sponsored by the Apache Incubator.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other
successful ASF projects. While incubation status is not necessarily a
reflection of the completeness or stability of the code, it does
indicate that the project has yet to be fully endorsed by the ASF.