Strange 3rd party service. We may could send a mail to ask what the service
vendor could do to fix this?
But at least, this doesn't look like a block to me.
I think basically, we could start the official vote on the dev for
graduation?
PPMC and dev team, WDYT?
Sheng Wu 吴晟
Twitter, wusheng1108
I check the website https://jitpack.io, it looks like they[1] crawling the
releases from GitHub directly, and then shade the groupId and artifactId by
their own rule.
The repo `dangdangdotcom/sharding-jdbc` is the previous repo before
entering incubator, we just transferred the repo to
Hi Justin,
Thanks for your prompt feedback, which always provides us valuable
instructions.
It seems like items currently remaining Errata is not a big issue, and the more
critical case is the brand thing. Besides, to make the website more 'Apache'
is another improvement. Make sense, and we
This domain [1] is created by 2019-06-28T10:15:48Z, which is after entering
the incubator.
The website has no relationship with Apache ShardingSphere. Do we need to
do anything about it?
[1] http://shardingsphere.io
--
Liang Zhang (John)
Apache ShardingSphere & Dubbo
Justin
Hi,
IMO it's not immediately obvious from the project web site that this is an
Apache project. It probably meets the minimum requirements but it would be nice
to see more than that.
Thanks,
Justin
Hi,
> 1 Project does not have 'commits' mailing list
You have notifications@ so that fine.
> 2 Has not provided an issue tracker link
You have this well documented on your website, so not a big issue, but it’s
also easy to fix.
> 3 Has not provided a wiki link
You have a wiki [1] and can
Hello folks,
With the help of the community (Specially thinks to Yue Zhao), Podling Website
Check page[1] said the status of our website is healthy.
However, three items below still stay in Errata of the incubator status
page[2]. The 2nd to 3rd items have joined our website[3][4],
and my
> I found there is a small issue about the copyright year on the NOTICE
> file, it should be 2018-2020 instead of 2019-2020, we can fix it in
> the next release.
Got it, we will revise the copyright to 2018-2020 in the next version
--
Zhao Jun (cherrylzhao)
Apache ShardingSphere
+1.
I checked:
- Download links are valid.
- Nexus staging files are OK for me.
- Checksums and PGP signature are valid.
- DISCLAIMER file is included.
- Both LICENSE and NOTICE files are just fine.
- No binary file in the source.
I found there is a small issue about the copyright year on the
> On Feb 25, 2020, at 6:47 AM, zhaojun wrote:
>
> Hello ShardingSphere Community,
>
> This is a call for vote to release Apache ShardingSphere (Incubating)
> version 4.0.1
Please vote accordingly:
[x] +1 approve
Checklist for reference:
[x] Download links are valid.
[x] Checksums and
10 matches
Mail list logo
