Hi,
I have drafted a script that aims at automate the whole process when preparing
an Apache release. The script can be found here[1].
It’s not production ready yet, but we can further improve it during the next
release.
Please help with me to make it better.
1.
https://github.com/apache/incu
Oh, my bad. I thought this vote has lasted for 72+ hours, I must have
misremembered the starting date.
Let’s wait some extra time here.
Best regards,
Jun
> On 1 Sep 2018, at 10:24, Justin Mclean wrote:
>
> Hi,
>
> It’s best to keep votes open for a minimum of 72 hours before announcing the
Hi,
It’s best to keep votes open for a minimum of 72 hours before announcing the
results.
Thanks,
Justin
We’ve received 3 +1 binding votes and one +1 non-binding vote:
+1 binding, Ian Luo
+1 binding, Huxing Zhang
+1 binding, Jun Liu
+1 non-binding, Jerrick
I will create a new vote thread in Apache community now.
Best regards,
Jun
> On 29 Aug 2018, at 13:14, Jun Liu wrote:
>
> Hello Dubbo Communi
Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 19 September 2018, 10:30 am PDT.
The report for your podling will fo
> mvn clean test # This will run all unit tests
> # you can also open rat and style plugin to check if every file meets
> requirements.
> mvn clean test -Drat.skip=false -Dcheckstyle.skip=false
>
> I suggest to use a dedicate profile for release, which will including
> all the checks, rat, checkst
