Good catch for Apache Way, hoping more and more our native guys to learn more
about the ways to build a health and diversity community :-)
Best Regards,
Von Gosling
> 在 2018年10月16日,10:47,yuhang xiu 写道:
>
> 应该
be recorded in the next release checklist. Such as,
not all source files have apache headers(nat are not always work well), odd
unzip file name etc.
Best Regards,
Von Gosling
> 在 2018年5月16日,10:55,Justin Mclean <jus...@classsoftware.com> 写道:
>
> Hi,
>
> +1 (binding)
>
>
e we ask for the
release manager, right ? Here is some hint[1] about release process from other
Apache Project.
[1] http://rocketmq.apache.org/docs/release-manual
Best Regards,
Von Gosling
> 在 2018年4月19日,08:48,Justin Mclean <jus...@classsoftware.com> 写道:
>
> Hi,
>
>&
Hi,
I would like to recommend that we’d better to finish the repository transfer
and some other necessary polish before the first release. Any questions for
that process, my pleasure to help :-)
Best Regards,
Von Gosling
> 在 2018年3月16日,17:06,Huxing Zhang <hux...@apache.org> 写道
Hi,
I really suggest we could be better to transfer the code to the ASF at the
first stage. But one complicated point around my hat, how could we arrange the
repositories in the Apache Git Repository? if we hope to keep the same release
pace with so many repositories.
Best Regards,
Von
Agree, security issues could be moved on the private email list to discuss :-)
Best Regards,
Von Gosling
> 在 2018年3月2日,11:59,Justin Mclean <jus...@classsoftware.com> 写道:
>
> Note that as an exception to the usual talk about it on the dev list
> dicussion should be kep
Hi,
It seems that email notification is not work well. Also, if we hope to receive
all issues, we must subscribe issue email list -
issues-subscr...@dubbo.incubator.apache.org
<mailto:issues-subscr...@dubbo.incubator.apache.org>.
Best Regards,
Von Gosling
> 在 2018年2月26日,15:15,Hux