You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by dongeforever <10...@qq.com> on 2017/01/16 09:39:09 UTC
[DISCUSS] Releasing a few versions supporting essential JMS features for Sub-project RocketMQ-JMS
Rename the subject for discussion.
Supporting JMS totally may take a long time.
It is free to start a branch for fully implementation.
Concurrently, we'd better release earlier versions to get some benefits:
1. support urgent users as quickly as possible
2. collect feedbacks from early users
And please let me know your thoughts.
------------------ Original ------------------
From: "zhangke";<zh...@foxmail.com>;
Date: Sat, Jan 14, 2017 10:25 AM
To: "dev"<de...@rocketmq.incubator.apache.org>;
Subject: Sub-project named RocketMQ-JMS has been started
Hi folks,
We have started a sub-project of RMQ named RocketMQ-JMS at the address https://github.com/rocketmq/rocketmq-jms. Our target is to support JMS2.0 Specification using RMQ as a JMS Provider. JMS is a protocol used widely in java world, providing another low latency and high available implement is a valuable and exciting thing.
As there a implement following parts of JMS1.1 Spec has been running stably in production environment for about a year, we decide to evolve upon that version in the beginning. But along with going deep into more JMS 2.0 details, we have divergent opinion about releasing a few versions supporting essential JMS features earlier or releasing a milestone version supporting protocol fully. We already have a small discussion in github issue: https://github.com/rocketmq/rocketmq-jms/issues/1 . I really appreciate you could give us some opinions.
Thanks!
Rick Zhang
Architect
ThoughtWorks
Re: [DISCUSS] Releasing a few versions supporting essential
JMSfeatures for Sub-project RocketMQ-JMS
Posted by 张轲 <zh...@gmail.com>.
sorry, the ISSUE link seems missing. The complete url:
https://github.com/rocketmq/rocketmq-jms/issues/1
2017-01-17 9:07 GMT+08:00 zhangke <zh...@foxmail.com>:
> Hi Willem,
> We haven't draw up a specific plan yet. Now we are still in discussion
> about the developing strategies mentioned in this mail's topic. If you have
> time, could you glance over this issue to give us some opinion?
>
> Now we host the RocketMQ-JMS module in the Github and won't affect the
> release process of RocketMQ. So this topic is just a discussion about
> RocketMQ-JMS irrelevant with RMQ releasing, but we hope to get some help :-)
>
>
> ------------------ 原始邮件 ------------------
> 发件人: "Willem Jiang";<wi...@gmail.com>;
> 发送时间: 2017年1月16日(星期一) 晚上6:37
> 收件人: "dev"<de...@rocketmq.incubator.apache.org>;
>
> 主题: Re: [DISCUSS] Releasing a few versions supporting essential
> JMSfeatures for Sub-project RocketMQ-JMS
>
>
>
> What's the development plan of the RocketMQ-JMS module?
> Do we need to host the RocketMQ-JMS module in the Apache git repo ?
>
> If we host the module in the Github, I don't think development of
> RocketMQ-JMS could affect the release process of RocketMQ.
> If we host the module in Apache RocketMQ repo, that is another story.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jan 16, 2017 at 5:39 PM, dongeforever <10...@qq.com> wrote:
>
> > Rename the subject for discussion.
> >
> >
> > Supporting JMS totally may take a long time.
> > It is free to start a branch for fully implementation.
> > Concurrently, we'd better release earlier versions to get some benefits:
> > 1. support urgent users as quickly as possible
> > 2. collect feedbacks from early users
> >
> >
> > And please let me know your thoughts.
> >
> >
> >
> >
> >
> >
> > ------------------ Original ------------------
> > From: "zhangke";<zh...@foxmail.com>;
> > Date: Sat, Jan 14, 2017 10:25 AM
> > To: "dev"<de...@rocketmq.incubator.apache.org>;
> >
> > Subject: Sub-project named RocketMQ-JMS has been started
> >
> >
> >
> > Hi folks,
> >
> >
> > We have started a sub-project of RMQ named RocketMQ-JMS at the
> address
> > https://github.com/rocketmq/rocketmq-jms. Our target is to support
> JMS2.0
> > Specification using RMQ as a JMS Provider. JMS is a protocol used widely
> > in java world, providing another low latency and high available implement
> > is a valuable and exciting thing.
> >
> >
> > As there a implement following parts of JMS1.1 Spec has been running
> > stably in production environment for about a year, we decide to evolve
> upon
> > that version in the beginning. But along with going deep into more JMS
> 2.0
> > details, we have divergent opinion about releasing a few versions
> > supporting essential JMS features earlier or releasing a milestone
> version
> > supporting protocol fully. We already have a small discussion in github
> > issue: https://github.com/rocketmq/rocketmq-jms/issues/1 . I really
> > appreciate you could give us some opinions.
> >
> >
> > Thanks!
> >
> >
> > Rick Zhang
> > Architect
> > ThoughtWorks
回复： [DISCUSS] Releasing a few versions supporting essential JMSfeatures for Sub-project RocketMQ-JMS
Posted by zhangke <zh...@foxmail.com>.
Hi Willem,
We haven't draw up a specific plan yet. Now we are still in discussion about the developing strategies mentioned in this mail's topic. If you have time, could you glance over this issue to give us some opinion?
Now we host the RocketMQ-JMS module in the Github and won't affect the release process of RocketMQ. So this topic is just a discussion about RocketMQ-JMS irrelevant with RMQ releasing, but we hope to get some help :-)
------------------ 原始邮件 ------------------
发件人: "Willem Jiang";<wi...@gmail.com>;
发送时间: 2017年1月16日(星期一) 晚上6:37
收件人: "dev"<de...@rocketmq.incubator.apache.org>;
主题: Re: [DISCUSS] Releasing a few versions supporting essential JMSfeatures for Sub-project RocketMQ-JMS
What's the development plan of the RocketMQ-JMS module?
Do we need to host the RocketMQ-JMS module in the Apache git repo ?
If we host the module in the Github, I don't think development of
RocketMQ-JMS could affect the release process of RocketMQ.
If we host the module in Apache RocketMQ repo, that is another story.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Jan 16, 2017 at 5:39 PM, dongeforever <10...@qq.com> wrote:
> Rename the subject for discussion.
>
>
> Supporting JMS totally may take a long time.
> It is free to start a branch for fully implementation.
> Concurrently, we'd better release earlier versions to get some benefits:
> 1. support urgent users as quickly as possible
> 2. collect feedbacks from early users
>
>
> And please let me know your thoughts.
>
>
>
>
>
>
> ------------------ Original ------------------
> From: "zhangke";<zh...@foxmail.com>;
> Date: Sat, Jan 14, 2017 10:25 AM
> To: "dev"<de...@rocketmq.incubator.apache.org>;
>
> Subject: Sub-project named RocketMQ-JMS has been started
>
>
>
> Hi folks,
>
>
> We have started a sub-project of RMQ named RocketMQ-JMS at the address
> https://github.com/rocketmq/rocketmq-jms. Our target is to support JMS2.0
> Specification using RMQ as a JMS Provider. JMS is a protocol used widely
> in java world, providing another low latency and high available implement
> is a valuable and exciting thing.
>
>
> As there a implement following parts of JMS1.1 Spec has been running
> stably in production environment for about a year, we decide to evolve upon
> that version in the beginning. But along with going deep into more JMS 2.0
> details, we have divergent opinion about releasing a few versions
> supporting essential JMS features earlier or releasing a milestone version
> supporting protocol fully. We already have a small discussion in github
> issue: https://github.com/rocketmq/rocketmq-jms/issues/1 . I really
> appreciate you could give us some opinions.
>
>
> Thanks!
>
>
> Rick Zhang
> Architect
> ThoughtWorks
Re: [DISCUSS] Releasing a few versions supporting essential JMS
features for Sub-project RocketMQ-JMS
Posted by Willem Jiang <wi...@gmail.com>.
What's the development plan of the RocketMQ-JMS module?
Do we need to host the RocketMQ-JMS module in the Apache git repo ?
If we host the module in the Github, I don't think development of
RocketMQ-JMS could affect the release process of RocketMQ.
If we host the module in Apache RocketMQ repo, that is another story.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Mon, Jan 16, 2017 at 5:39 PM, dongeforever <10...@qq.com> wrote:
> Rename the subject for discussion.
>
>
> Supporting JMS totally may take a long time.
> It is free to start a branch for fully implementation.
> Concurrently, we'd better release earlier versions to get some benefits:
> 1. support urgent users as quickly as possible
> 2. collect feedbacks from early users
>
>
> And please let me know your thoughts.
>
>
>
>
>
>
> ------------------ Original ------------------
> From: "zhangke";<zh...@foxmail.com>;
> Date: Sat, Jan 14, 2017 10:25 AM
> To: "dev"<de...@rocketmq.incubator.apache.org>;
>
> Subject: Sub-project named RocketMQ-JMS has been started
>
>
>
> Hi folks,
>
>
> We have started a sub-project of RMQ named RocketMQ-JMS at the address
> https://github.com/rocketmq/rocketmq-jms. Our target is to support JMS2.0
> Specification using RMQ as a JMS Provider. JMS is a protocol used widely
> in java world, providing another low latency and high available implement
> is a valuable and exciting thing.
>
>
> As there a implement following parts of JMS1.1 Spec has been running
> stably in production environment for about a year, we decide to evolve upon
> that version in the beginning. But along with going deep into more JMS 2.0
> details, we have divergent opinion about releasing a few versions
> supporting essential JMS features earlier or releasing a milestone version
> supporting protocol fully. We already have a small discussion in github
> issue: https://github.com/rocketmq/rocketmq-jms/issues/1 . I really
> appreciate you could give us some opinions.
>
>
> Thanks!
>
>
> Rick Zhang
> Architect
> ThoughtWorks