[RESULT][VOTE]rocketmq-ons 1.0.0 release

[heng du <du...@gmail.com>]

Hello RocketMQ Community,

The Apache rocketmq-ons 1.0.0 vote is now closed and has passed with [4]
binding +1s, [3] non-binding +1s and no 0 or -1:

*Binding votes +1s:*
dongeforever

Vongosling

duhengforever

ShannonDing

*Non-binding votes +1s:*

JonnXu

huzongtang

chengxiangwang

Thanks for everyone's reply, the release will be published soon.

Thanks,
The Apache RocketMQ Team

chengxiangwang@cmss.chinamobile.com <ch...@cmss.chinamobile.com>
于2019年7月12日周五 下午2:27写道：

> +1
>
> ------------------------------
> 程 向往（Cheng Xiangwang）
> 中移（苏州）软件技术有限公司
> 云计算产品部
> 电话：18896725053
> 邮箱：chengxiangwang@cmss.chinamobile.com <zo...@cmss.chinamobile.com>
> 地址：苏州市高新区科灵路78号苏高新软件园10幢
>
>
> *From:* Du Heng <du...@apache.org>
> *Date:* 2019-07-12 13:58
> *To:* users@rocketmq.apache.org
> *Subject:* Re: [VOTE]rocketmq-ons 1.0.0 release
> +1
>
> On 2019/07/12 05:49:08, heng du <du...@gmail.com> wrote:
> > Hello RocketMQ Community,
> >
> > This is the vote for the 1.0.0 release of Apache ONS client, and it's
> also
> > the first release of apache rocketmq-ons.
> >
> > Github repo: *https://github.com/apache/rocketmq-
> > <https://github.com/apache/rocketmq-spring>ons*
> >
> > Based on the discussion previous[1], the Apache RocketMQ community
> developed
> > a lightweight client named as ONS. Currently, this client has implemented
> > all the basic features related to Producer/Consumer, and at the same
> time,
> > order/batch/transactional message, etc. advanced features are also
> > supported in this client. This also indicates that the client already
> has a
> > high maturity. So, in order to continually improve this lightweight
> > client, we hope to release the first version and optimize the client
> based
> > on the problems found during the actual production environment use
> process.
> >
> > In summary, in this release, those features below are supported:
> >
> >    - Produce messages, including normal, transactional, delayed messages,
> >    in synchronously, asynchronously and oneway model.
> >    - Consume messages, in cluster or broadcast model, concurrently and
> >    orderly with push consumer
> >    - Automatically rebalanced, both in producing and consuming process.
> >    - Reliability, any downtime broker or name server has no impact on the
> >    client.
> >
> >
> > Please vote accordingly:
> >
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > [1]
> >
> https://lists.apache.org/thread.html/0b2dfbb3b722bb8d710d8bd9d264d51013153608934d1a1c90c810de@%3Cusers.rocketmq.apache.org%3E
> > ,
> > Thanks,
> > The Apache RocketMQ Team
> >
> >
> > ---------- Forwarded message ---------
> > 发件人： heng du <du...@gmail.com>
> > Date: 2019年7月5日周五 下午3:14
> > Subject: [DISCUSS]rocketmq-ons 1.0.0 release
> > To: dev <de...@rocketmq.apache.org>
> > Cc: users <us...@rocketmq.apache.org>
> >
> >
> > Hello RocketMQ Community,
> >
> > This is the discussion for the release of rocketmq-ons 1.0.0.
> >
> > As discussed in the mailing list:
> >
> https://lists.apache.org/thread.html/0b2dfbb3b722bb8d710d8bd9d264d51013153608934d1a1c90c810de@%3Cusers.rocketmq.apache.org%3E
> ,
> > most of rocketmq users think it would be nice if there's a lightweight
> > client. and most of rocketmq users agree that the light-weight client
> > should be a high-level client that provides better abstraction and hide
> the
> > internal concepts and
> > implementation details as much as possible. Most important of all, to be
> on
> > the safe side, the new client should remove the admin interface, because
> of
> > the admin interface directly expose to the ordinary developer will pose a
> > risk to the server side.
> >
> > Based on the discussion above, the rocketmq community developed a
> > lightweight client named as ONS. Currently, this client has implemented
> all
> > the basic features related to Producer/Consumer, and at the same time,
> > order/batch/transactional message, etc. advanced features are also
> > supported in this client. This also indicates that the client already
> has a
> > high maturity. So, in order to continually improve this lightweight
> > client, we hope to release the first version and optimize the client
> based
> > on the problems found during the actual production environment use
> process.
> >
> > Welcome everyone to comment in this email, and if no other sounds, I
> would
> > like to call for a vote for this release :-)
> >
> > Thanks,
> > The Apache RocketMQ Team
> >
>
>