typo when talking about PIPs. s/sever/several/

-Ivan

On Wed, Mar 13, 2019 at 6:47 AM Matteo Merli <mme...@apache.org> wrote:
>
> ## Description:
>
> 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, automatic cursor management for
> subscribers, and cross-datacenter replication.
>
> ## Issues:
>  - There are no issues requiring board attention at this time.
>
> ## Activity:
>   - The project has released 2.2.0 in Febrary. This was a very big release
>     that included many new features and improvements.
>     Highlights include:
>      * Kubernetes support in Pulsar functions
>      * New Pulsar IO connectors: Change data capture with Debezium, MongoDB,
>        Elastic Search, HBase and local files source and sink.
>      * Token based authentication
>      * Schema support in Python client library
>      * Function state API in Python
>   - Several meetup and conferences talk on Pulsar
>     * Two talks are scheduled for Strata SF in March:
>       - How Zhaopin.com built its enterprise event bus using Apache Pulsar
>       from Sijie and Pengui
>       - Reducing stream processing complexity using Apache Pulsar Functions
>       from Jowanza Joseph and Karthik Ramasamy
>   - A patch release (2.3.1) is being prepared to address all the issues 
> reported
>     in 2.3.0 release
>   - Work is ongoing for next release (2.4.0), scheduled for end of
> December for which
>     we plan to include:
>     * NodeJS client library
>     * Negative acknowledgments
>     * Replicated subscription state
>   - Since last report sever PIPs (Pulsar improvement proposals) were 
> submitted:
>     * PIP 32: Go Function API, Instance and LocalRun
>     * PIP 31: Transaction Support
>     * PIP 30: change authentication provider API to support mutual
> authentication
>     * PIP 28: Pulsar Proxy Gateway Improvement
>     * PIP 29: One package for both pulsar-client and pulsar-admin
>     * PIP 26: Delayed Message Delivery
>
> ## Health report:
>   - There is healthy grow in the community
>   - Activity on the Slack channel is still high, many first time users come
>     to ask questions while getting started. There are 103 weekly active users
>     on the channel, up from 92 in November.
>
> ## PMC changes:
>
>  - Currently 23 PMC members
>  - No new PMC added since last report
>
> ## Committer base changes:
>
>  - Currently 24 committers
>  - Last committer added: Penghui Li - Dec 7th
>
> ## Releases:
>
>   - 2.2.1 was released on Dec. 31st 2018
>   - 2.3.0 was released on Feb. 20th 2019
>
> ## Mailing list activity:
>
>  - Activity on the mailing lists remains high with a mixture of new users,
>    contributors, and deeper more experienced users and contributors sparking
>    discussion and questions and filing bugs or new features.
>
>  - us...@pulsar.apache.org:
>     - 94 subscribers (+10 from Dec 2018) - 103 emails sent to list in
> last 3 months
>
>  - dev@pulsar.apache.org:
>     - 97 subscribers (+17 from Dec 2018) - 241 emails sent to list in
> last 3 months
>
>
> ## GitHub activity:
>
>  - 386 PR from 47 contributors were merged in the last 3 months (up from 131)
>  - 197 Issues were created and 125 closed in the last 3 months
>
>
> --
> Matteo Merli
> <mme...@apache.org>

Reply via email to