You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@rocketmq.apache.org by yukon <yu...@apache.org> on 2017/03/15 08:40:55 UTC
The sub projects' migration work has been completed
Hi guys,
We have migrated three sub projects from rocketmq community to apache
repo.[1]
And there are three JIRA components have been created for sub projects:
1. rocketmq-jms
2. rocketmq-console-ng
3. rocketmq-flume-ng
[1]. https://github.com/apache/incubator-rocketmq-externals
Regards,
yukon
[DISCUSS] How to handle Ip-clearance for apache rocketmq community
projects
Posted by Von Gosling <vo...@apache.org>.
Rename mail name, adding some context we have discussed before.
Hi,
As topic description, I would like to put forward this issue despite we are apache tlp project. Firstly. we must arrange the total projects outside of Apache Repository[3]. According to my work on Apache RocketMQ Externals, CPP client[1] is a contribution from Alibaba, which is outside of Apache Repository. Anyone could add else ? If no, I suggest we re-check what we have done about all external projects [2].
[1] https://github.com/apache/rocketmq-externals/tree/master/rocketmq-cpp
[2] https://github.com/apache/rocketmq-externals
[3] http://incubator.apache.org/ip-clearance/
Best Regards,
Von Gosling
> 在 2017年3月20日，17:04，Von Gosling <vo...@apache.org> 写道：
>
> Hi,
>
>> Perhaps like Justin
>> said above, getting ICLAs from the contributors and having the potential
>> committer discussion about each of them right away.
>
>
>
> Actually, i was also puzzled about this contribution behavior coming from some Apache Project Community. I have been investing other Apache TLP works about here. They get them involved in through the same git repository, or leave them alone, just through one formal link to touch these community projects. But as for us, we hope to merge the mature project to our repository, let it under Apache RocketMQ’s umbrella. So, that’s why we provided the Github group RocketMQ firstly, hoping to gathering them together. We define the mature project as those were used in product environment massively, like the RocketMQ-JMS and RocketMQ-Console projects from the RocketMQ’s first marathon campaign :-)
>
>
>> 在 2017年3月19日，01:26，Bruce Snyder <br...@gmail.com> 写道：
>>
>> Thanks for raising this question, Justin, as there is an important
>> distinction here.
>>
>> Since the code that was not part of the core RocketMQ and was recently
>> moved to the externals project was not migrated as part of the original
>> move from Github to the ASF, it must be treated a bit differently. This is
>> especially true if folks who are not currently committers to the ASF
>> RocketMQ project contributed to that code. We should have taken a more
>> formal approach to moving over this code (my mistake for not recognizing
>> this sooner). In terms of voting in the folks who contributed to this code
>> when it resided at Github vs. now that it resides at the ASF, there must be
>> a formal discussion of this amongst the PPMC about these potential
>> committers in order to make this decision just like any other potential
>> committers.
>>
>> It's also important to recognize that the ASF cannot provide the same legal
>> guarantees for code that was not officially contributed to the ASF vs. code
>> that goes through the proper legal process that has been established over
>> the years at the ASF (like the original core RocketMQ code went through).
>> This what code grants are all about and an important tenant of why the ASF
>> exists. I'm honestly not quite sure what to do here. Perhaps like Justin
>> said above, getting ICLAs from the contributors and having the potential
>> committer discussion about each of them right away.
>>
>> Justin, what are your further thoughts on this second topic?
>>
>> Bruce
>>
>> On Thu, Mar 16, 2017 at 8:43 PM, Justin Mclean <ju...@classsoftware.com>
>> wrote:
>>
>>> Hi,
>>>
>>>> And we want to adopt the same way in the second code marathon:
>>>> 1. Launch and develop the sub project in [1] at the initial stage.
>>>> 2. Migrate the stable and fully functional sub projects to
>>>> rocketmq-externals, meanwhile vote the top contributors as a committer.
>>>>
>>>> Does it ok ?
>>>
>>> I think I have a couple of issues with this:
>>> 1. Code that hasn’t been reviewed for possible IP or legal issues is
>>> copied into the Apache repo.
>>> 2. We may not have ICLAs for the contributors.
>>> 3. You are voting on committer based on their contribution to an external
>>> project not this Apache project.
>>>
>>> What do the other mentors think?
>>>
>>> Thanks,
>>> Justin
>>
>>
>>
>>
>> --
>> perl -e 'print
>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
>>
>> ActiveMQ in Action: http://bit.ly/2je6cQ
>> Blog: http://bsnyder.org/ <http://bruceblog.org/>
>> Twitter: http://twitter.com/brucesnyder
>
Re: The sub projects' migration work has been completed
Posted by Von Gosling <vo...@apache.org>.
Hi,
> Perhaps like Justin
> said above, getting ICLAs from the contributors and having the potential
> committer discussion about each of them right away.
Actually, i was also puzzled about this contribution behavior coming from some Apache Project Community. I have been investing other Apache TLP works about here. They get them involved in through the same git repository, or leave them alone, just through one formal link to touch these community projects. But as for us, we hope to merge the mature project to our repository, let it under Apache RocketMQ’s umbrella. So, that’s why we provided the Github group RocketMQ firstly, hoping to gathering them together. We define the mature project as those were used in product environment massively, like the RocketMQ-JMS and RocketMQ-Console projects from the RocketMQ’s first marathon campaign :-)
> 在 2017年3月19日，01:26，Bruce Snyder <br...@gmail.com> 写道：
>
> Thanks for raising this question, Justin, as there is an important
> distinction here.
>
> Since the code that was not part of the core RocketMQ and was recently
> moved to the externals project was not migrated as part of the original
> move from Github to the ASF, it must be treated a bit differently. This is
> especially true if folks who are not currently committers to the ASF
> RocketMQ project contributed to that code. We should have taken a more
> formal approach to moving over this code (my mistake for not recognizing
> this sooner). In terms of voting in the folks who contributed to this code
> when it resided at Github vs. now that it resides at the ASF, there must be
> a formal discussion of this amongst the PPMC about these potential
> committers in order to make this decision just like any other potential
> committers.
>
> It's also important to recognize that the ASF cannot provide the same legal
> guarantees for code that was not officially contributed to the ASF vs. code
> that goes through the proper legal process that has been established over
> the years at the ASF (like the original core RocketMQ code went through).
> This what code grants are all about and an important tenant of why the ASF
> exists. I'm honestly not quite sure what to do here. Perhaps like Justin
> said above, getting ICLAs from the contributors and having the potential
> committer discussion about each of them right away.
>
> Justin, what are your further thoughts on this second topic?
>
> Bruce
>
> On Thu, Mar 16, 2017 at 8:43 PM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
>> Hi,
>>
>>> And we want to adopt the same way in the second code marathon:
>>> 1. Launch and develop the sub project in [1] at the initial stage.
>>> 2. Migrate the stable and fully functional sub projects to
>>> rocketmq-externals, meanwhile vote the top contributors as a committer.
>>>
>>> Does it ok ?
>>
>> I think I have a couple of issues with this:
>> 1. Code that hasn’t been reviewed for possible IP or legal issues is
>> copied into the Apache repo.
>> 2. We may not have ICLAs for the contributors.
>> 3. You are voting on committer based on their contribution to an external
>> project not this Apache project.
>>
>> What do the other mentors think?
>>
>> Thanks,
>> Justin
>
>
>
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bsnyder.org/ <http://bruceblog.org/>
> Twitter: http://twitter.com/brucesnyder
Re: The sub projects' migration work has been completed
Posted by Bruce Snyder <br...@gmail.com>.
Thanks for raising this question, Justin, as there is an important
distinction here.
Since the code that was not part of the core RocketMQ and was recently
moved to the externals project was not migrated as part of the original
move from Github to the ASF, it must be treated a bit differently. This is
especially true if folks who are not currently committers to the ASF
RocketMQ project contributed to that code. We should have taken a more
formal approach to moving over this code (my mistake for not recognizing
this sooner). In terms of voting in the folks who contributed to this code
when it resided at Github vs. now that it resides at the ASF, there must be
a formal discussion of this amongst the PPMC about these potential
committers in order to make this decision just like any other potential
committers.
It's also important to recognize that the ASF cannot provide the same legal
guarantees for code that was not officially contributed to the ASF vs. code
that goes through the proper legal process that has been established over
the years at the ASF (like the original core RocketMQ code went through).
This what code grants are all about and an important tenant of why the ASF
exists. I'm honestly not quite sure what to do here. Perhaps like Justin
said above, getting ICLAs from the contributors and having the potential
committer discussion about each of them right away.
Justin, what are your further thoughts on this second topic?
Bruce
On Thu, Mar 16, 2017 at 8:43 PM, Justin Mclean <ju...@classsoftware.com>
wrote:
> Hi,
>
> > And we want to adopt the same way in the second code marathon:
> > 1. Launch and develop the sub project in [1] at the initial stage.
> > 2. Migrate the stable and fully functional sub projects to
> > rocketmq-externals, meanwhile vote the top contributors as a committer.
> >
> > Does it ok ?
>
> I think I have a couple of issues with this:
> 1. Code that hasn’t been reviewed for possible IP or legal issues is
> copied into the Apache repo.
> 2. We may not have ICLAs for the contributors.
> 3. You are voting on committer based on their contribution to an external
> project not this Apache project.
>
> What do the other mentors think?
>
> Thanks,
> Justin
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bsnyder.org/ <http://bruceblog.org/>
Twitter: http://twitter.com/brucesnyder
Re: The sub projects' migration work has been completed
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> And we want to adopt the same way in the second code marathon:
> 1. Launch and develop the sub project in [1] at the initial stage.
> 2. Migrate the stable and fully functional sub projects to
> rocketmq-externals, meanwhile vote the top contributors as a committer.
>
> Does it ok ?
I think I have a couple of issues with this:
1. Code that hasn’t been reviewed for possible IP or legal issues is copied into the Apache repo.
2. We may not have ICLAs for the contributors.
3. You are voting on committer based on their contribution to an external project not this Apache project.
What do the other mentors think?
Thanks,
Justin
Re: The sub projects' migration work has been completed
Posted by Xinyu Zhou <zh...@xinyu.im>.
Hi Bruce,
Sure, we will announce it before the preparation work has been finished.
Thanks, yukon
On Thu, Mar 16, 2017 at 10:16 PM, Bruce Snyder <br...@gmail.com>
wrote:
Hi Yukon,
Sounds good. If you're having code marathons, you should be having
discussions about this on the dev@ and users@ mailing lists in order to
advertise them more to users so that they can participate remotely.
Bruce
On Wed, Mar 15, 2017 at 8:36 PM, yukon <yu...@apache.org> wrote:
> Hi Bruce,
>
> All the projects in [1] have been moved to repo
> `incubator-rocketmq-externals` except `rocketmq-storm`,
> which will be migrated to Apache Storm repo by Xin Wang.
>
> These three projects are the outputs of our first marathon activity[2],
and
> we want to start the second code marathon
> which will cover the database replicator, multi-language client and big
> data platform.
>
> And we want to adopt the same way in the second code marathon:
>
> 1. Launch and develop the sub project in [1] at the initial stage.
> 2. Migrate the stable and fully functional sub projects to
> rocketmq-externals, meanwhile vote the top contributors as a committer.
>
> Does it ok ?
>
> If we start the sub projects in rocketmq-externals directly, the every
step
> needs a committer involved in it, it's very inconvenient.
>
> [1]. https://github.com/rocketmq
> [2].
> http://rocketmq.incubator.apache.org/activity/launch-
> rocketmq-code-marathon/
>
> Regards,
> yukon
>
> On Thu, Mar 16, 2017 at 12:49 AM, Bruce Snyder <br...@gmail.com>
> wrote:
>
> > Thank you, Yukon. Are there any projects that have not been migrated
from
> > Github? I am asking because it would be helpful to point the entire
> Github
> > project at the ASF Incubating project.
> >
> > Bruce
> >
> > On Wed, Mar 15, 2017 at 2:40 AM, yukon <yu...@apache.org> wrote:
> >
> > > Hi guys,
> > >
> > > We have migrated three sub projects from rocketmq community to
apache
> > > repo.[1]
> > >
> > > And there are three JIRA components have been created for sub
projects:
> > > 1. rocketmq-jms
> > > 2. rocketmq-console-ng
> > > 3. rocketmq-flume-ng
> > >
> > > [1]. https://github.com/apache/incubator-rocketmq-externals
> > >
> > >
> > > Regards,
> > > yukon
> > >
> >
> >
> >
> > --
> > perl -e 'print
> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
> >
> > ActiveMQ in Action: http://bit.ly/2je6cQ
> > Blog: http://bsnyder.org/ <http://bruceblog.org/>
> > Twitter: http://twitter.com/brucesnyder
> >
>
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bsnyder.org/ <http://bruceblog.org/>
Twitter: http://twitter.com/brucesnyder
Re: The sub projects' migration work has been completed
Posted by Bruce Snyder <br...@gmail.com>.
Hi Yukon,
Sounds good. If you're having code marathons, you should be having
discussions about this on the dev@ and users@ mailing lists in order to
advertise them more to users so that they can participate remotely.
Bruce
On Wed, Mar 15, 2017 at 8:36 PM, yukon <yu...@apache.org> wrote:
> Hi Bruce,
>
> All the projects in [1] have been moved to repo
> `incubator-rocketmq-externals` except `rocketmq-storm`,
> which will be migrated to Apache Storm repo by Xin Wang.
>
> These three projects are the outputs of our first marathon activity[2], and
> we want to start the second code marathon
> which will cover the database replicator, multi-language client and big
> data platform.
>
> And we want to adopt the same way in the second code marathon:
>
> 1. Launch and develop the sub project in [1] at the initial stage.
> 2. Migrate the stable and fully functional sub projects to
> rocketmq-externals, meanwhile vote the top contributors as a committer.
>
> Does it ok ?
>
> If we start the sub projects in rocketmq-externals directly, the every step
> needs a committer involved in it, it's very inconvenient.
>
> [1]. https://github.com/rocketmq
> [2].
> http://rocketmq.incubator.apache.org/activity/launch-
> rocketmq-code-marathon/
>
> Regards,
> yukon
>
> On Thu, Mar 16, 2017 at 12:49 AM, Bruce Snyder <br...@gmail.com>
> wrote:
>
> > Thank you, Yukon. Are there any projects that have not been migrated from
> > Github? I am asking because it would be helpful to point the entire
> Github
> > project at the ASF Incubating project.
> >
> > Bruce
> >
> > On Wed, Mar 15, 2017 at 2:40 AM, yukon <yu...@apache.org> wrote:
> >
> > > Hi guys,
> > >
> > > We have migrated three sub projects from rocketmq community to apache
> > > repo.[1]
> > >
> > > And there are three JIRA components have been created for sub projects:
> > > 1. rocketmq-jms
> > > 2. rocketmq-console-ng
> > > 3. rocketmq-flume-ng
> > >
> > > [1]. https://github.com/apache/incubator-rocketmq-externals
> > >
> > >
> > > Regards,
> > > yukon
> > >
> >
> >
> >
> > --
> > perl -e 'print
> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
> >
> > ActiveMQ in Action: http://bit.ly/2je6cQ
> > Blog: http://bsnyder.org/ <http://bruceblog.org/>
> > Twitter: http://twitter.com/brucesnyder
> >
>
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bsnyder.org/ <http://bruceblog.org/>
Twitter: http://twitter.com/brucesnyder
Re: The sub projects' migration work has been completed
Posted by yukon <yu...@apache.org>.
Hi Bruce,
All the projects in [1] have been moved to repo
`incubator-rocketmq-externals` except `rocketmq-storm`,
which will be migrated to Apache Storm repo by Xin Wang.
These three projects are the outputs of our first marathon activity[2], and
we want to start the second code marathon
which will cover the database replicator, multi-language client and big
data platform.
And we want to adopt the same way in the second code marathon:
1. Launch and develop the sub project in [1] at the initial stage.
2. Migrate the stable and fully functional sub projects to
rocketmq-externals, meanwhile vote the top contributors as a committer.
Does it ok ?
If we start the sub projects in rocketmq-externals directly, the every step
needs a committer involved in it, it's very inconvenient.
[1]. https://github.com/rocketmq
[2].
http://rocketmq.incubator.apache.org/activity/launch-rocketmq-code-marathon/
Regards,
yukon
On Thu, Mar 16, 2017 at 12:49 AM, Bruce Snyder <br...@gmail.com>
wrote:
> Thank you, Yukon. Are there any projects that have not been migrated from
> Github? I am asking because it would be helpful to point the entire Github
> project at the ASF Incubating project.
>
> Bruce
>
> On Wed, Mar 15, 2017 at 2:40 AM, yukon <yu...@apache.org> wrote:
>
> > Hi guys,
> >
> > We have migrated three sub projects from rocketmq community to apache
> > repo.[1]
> >
> > And there are three JIRA components have been created for sub projects:
> > 1. rocketmq-jms
> > 2. rocketmq-console-ng
> > 3. rocketmq-flume-ng
> >
> > [1]. https://github.com/apache/incubator-rocketmq-externals
> >
> >
> > Regards,
> > yukon
> >
>
>
>
> --
> perl -e 'print
> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
>
> ActiveMQ in Action: http://bit.ly/2je6cQ
> Blog: http://bsnyder.org/ <http://bruceblog.org/>
> Twitter: http://twitter.com/brucesnyder
>
Re: The sub projects' migration work has been completed
Posted by Bruce Snyder <br...@gmail.com>.
Thank you, Yukon. Are there any projects that have not been migrated from
Github? I am asking because it would be helpful to point the entire Github
project at the ASF Incubating project.
Bruce
On Wed, Mar 15, 2017 at 2:40 AM, yukon <yu...@apache.org> wrote:
> Hi guys,
>
> We have migrated three sub projects from rocketmq community to apache
> repo.[1]
>
> And there are three JIRA components have been created for sub projects:
> 1. rocketmq-jms
> 2. rocketmq-console-ng
> 3. rocketmq-flume-ng
>
> [1]. https://github.com/apache/incubator-rocketmq-externals
>
>
> Regards,
> yukon
>
--
perl -e 'print
unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );'
ActiveMQ in Action: http://bit.ly/2je6cQ
Blog: http://bsnyder.org/ <http://bruceblog.org/>
Twitter: http://twitter.com/brucesnyder
Re: The sub projects' migration work has been completed
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Hi Yukon,
Thanks for the pointer!
Moving 'master' branch only is fine.
Roman
On Friday, March 17, 2017 11:08 AM, yukon <yu...@apache.org> wrote:
Hi Roman,
The commit history is here[1], and I only migrated the master branches and
the `jms-dev-1.1.0` branch to rocketmq-externals.
Do you have other branches need to be migrated?
[1]. https://github.com/apache/incubator-rocketmq-externals/commits/master
Regards,
yukon
On Fri, Mar 17, 2017 at 9:55 AM, Roman Shtykh <rs...@yahoo.com.invalid>
wrote:
> Hi Yukon,
> The commit history is lost.
> Roman
>
> On Wednesday, March 15, 2017 5:47 PM, yukon <yu...@apache.org> wrote:
>
>
> Hi guys,
>
> We have migrated three sub projects from rocketmq community to apache
> repo.[1]
>
> And there are three JIRA components have been created for sub projects:
> 1. rocketmq-jms
> 2. rocketmq-console-ng
> 3. rocketmq-flume-ng
>
> [1]. https://github.com/apache/incubator-rocketmq-externals
>
>
> Regards,
> yukon
>
>
>
>
Re: The sub projects' migration work has been completed
Posted by yukon <yu...@apache.org>.
Hi Roman,
The commit history is here[1], and I only migrated the master branches and
the `jms-dev-1.1.0` branch to rocketmq-externals.
Do you have other branches need to be migrated?
[1]. https://github.com/apache/incubator-rocketmq-externals/commits/master
Regards,
yukon
On Fri, Mar 17, 2017 at 9:55 AM, Roman Shtykh <rs...@yahoo.com.invalid>
wrote:
> Hi Yukon,
> The commit history is lost.
> Roman
>
> On Wednesday, March 15, 2017 5:47 PM, yukon <yu...@apache.org> wrote:
>
>
> Hi guys,
>
> We have migrated three sub projects from rocketmq community to apache
> repo.[1]
>
> And there are three JIRA components have been created for sub projects:
> 1. rocketmq-jms
> 2. rocketmq-console-ng
> 3. rocketmq-flume-ng
>
> [1]. https://github.com/apache/incubator-rocketmq-externals
>
>
> Regards,
> yukon
>
>
>
>
Re: The sub projects' migration work has been completed
Posted by Roman Shtykh <rs...@yahoo.com.INVALID>.
Hi Yukon,
The commit history is lost.
Roman
On Wednesday, March 15, 2017 5:47 PM, yukon <yu...@apache.org> wrote:
Hi guys,
We have migrated three sub projects from rocketmq community to apache
repo.[1]
And there are three JIRA components have been created for sub projects:
1. rocketmq-jms
2. rocketmq-console-ng
3. rocketmq-flume-ng
[1]. https://github.com/apache/incubator-rocketmq-externals
Regards,
yukon
Re: The sub projects' migration work has been completed
Posted by Xinyu Zhou <zh...@xinyu.im>.
Thanks, Justin
We will please the major contributors to provide ICLAs later.
Regards, yukon
On Fri, Mar 17, 2017 at 10:40 AM, Justin Mclean <ju...@classsoftware.com>
wrote:
Hi,
> We have migrated three sub projects from rocketmq community to apache
> repo.[1]
>
> And there are three JIRA components have been created for sub projects:
> 1. rocketmq-jms
> 2. rocketmq-console-ng
> 3. rocketmq-flume-ng
Do we have ICLAs [1] for all contributors? or at least the major
contributors?
IMO it probably would of be better to treating these as a software grant
[2], but probably a bit too late for that.
Thanks,
Justin
1.https://www.apache.org/dev/new-committers-guide.html#cla
2.https://www.apache.org/licenses/#grants
Re: The sub projects' migration work has been completed
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> We have migrated three sub projects from rocketmq community to apache
> repo.[1]
>
> And there are three JIRA components have been created for sub projects:
> 1. rocketmq-jms
> 2. rocketmq-console-ng
> 3. rocketmq-flume-ng
Do we have ICLAs [1] for all contributors? or at least the major contributors?
IMO it probably would of be better to treating these as a software grant [2], but probably a bit too late for that.
Thanks,
Justin
1.https://www.apache.org/dev/new-committers-guide.html#cla
2.https://www.apache.org/licenses/#grants
Re: The sub projects' migration work has been completed
Posted by yukon <yu...@apache.org>.
Hi Rick,
Sorry for that, I have migrated branch 'dev-1.1.0' to a new branch
'jms-dev-1.1.0'. [1]
[1].
https://github.com/apache/incubator-rocketmq-externals/tree/jms-dev-1.1.0
Regards,
yukon
On Wed, Mar 15, 2017 at 4:55 PM, Rick Zhang <zh...@gmail.com>
wrote:
> Hi yukon,
>
> The branch "dev-1.1.0" of rocketmq-jms has been lost. This branch is still
> useful at present as it may be the next generation.
>
> Regrads
>
> 2017-03-15 16:40 GMT+08:00 yukon <yu...@apache.org>:
>
> > Hi guys,
> >
> > We have migrated three sub projects from rocketmq community to apache
> > repo.[1]
> >
> > And there are three JIRA components have been created for sub projects:
> > 1. rocketmq-jms
> > 2. rocketmq-console-ng
> > 3. rocketmq-flume-ng
> >
> > [1]. https://github.com/apache/incubator-rocketmq-externals
> >
> >
> > Regards,
> > yukon
> >
>
Re: The sub projects' migration work has been completed
Posted by Rick Zhang <zh...@gmail.com>.
Hi yukon,
The branch "dev-1.1.0" of rocketmq-jms has been lost. This branch is still
useful at present as it may be the next generation.
Regrads
2017-03-15 16:40 GMT+08:00 yukon <yu...@apache.org>:
> Hi guys,
>
> We have migrated three sub projects from rocketmq community to apache
> repo.[1]
>
> And there are three JIRA components have been created for sub projects:
> 1. rocketmq-jms
> 2. rocketmq-console-ng
> 3. rocketmq-flume-ng
>
> [1]. https://github.com/apache/incubator-rocketmq-externals
>
>
> Regards,
> yukon
>