[GitHub] incubator-rocketmq issue #69: [ROCKETMQ-111] fix possible MQClientException ...

Github user zhouxinyu commented on the issue: https://github.com/apache/incubator-rocketmq/pull/69 Hi @yilingfeng @shroman , there is no need to open a new PR, the new commit will be merged to `develop` branch directly. --- If your project is set up for it, you can reply to this

Suggestions

Hi devs, Here are some suggestions about documents in rocketmq-site. 1. "Versioned" documents. 2. Some important parts are missing in documents: APIs, as well as examples (Producer, Consumer) Configurations (Broker, NameServer, Producer, Consumer) Thanks, Xin Wang (vesense)

[GitHub] incubator-rocketmq issue #72: [ROCKETMQ-134]the offset of message filter by ...

Github user coveralls commented on the issue: https://github.com/apache/incubator-rocketmq/pull/72 [](https://coveralls.io/builds/10498533) Changes Unknown when pulling

Re: Podling Report Reminder - March 2017

The commit mode (RTC vs. CTR) is up to the PPMC. As Justin mentioned, RTC can cause scalability issues. We should discuss it in the PPMC to come to a decision as a community. Bruce On Wed, Mar 8, 2017 at 2:48 AM, Justin Mclean wrote: > Hi, > > > we hope to one

Re: Podling Report Reminder - March 2017

Hi, Sorry if I misunderstand anything her or something is getting lost in translation. > As we have control for these repos, we are able to control the quality of > releases. Who is we here? The we should be Apache RocketMQ project not an external project on GitHub. > So the current state

Re: Podling Report Reminder - March 2017

Hi: Maybe we should think highly of encouragement instead of management. Just like https://github.com/rocketmq, all integration projects stay under the same organization instead of one repo. They are independent and also easy for users to find what they need. As we have control for these

[GitHub] incubator-rocketmq issue #68: [ROCKETMQ-107] fix possible concurrency proble...

Github user shroman commented on the issue: https://github.com/apache/incubator-rocketmq/pull/68 @Jaskey I agree that `setServiceState` should be deprecated. I overlooked it was _public_. --- If your project is set up for it, you can reply to this email and have your reply appear on