Thank you all.
I'm very happy to conclude this vote process with the release of version
0.0.4.
Cheers,
Lior
On Sat, Mar 5, 2022 at 4:38 PM Xun Liu wrote:
> +1 (binding)
>
> I have checked the following items:
> - Incubating in name
> - LICENSE and NOTICE are fine
> - DISCLAIMER exists
> - No
The vote passes with 15 +1 (binding) and 1 +1 (non-binding) vs. no -1s
Regards,
Dave
> On Feb 22, 2022, at 10:57 PM, Kevin Ratnasekera
> wrote:
>
> +1
>
> On Wed, Feb 23, 2022 at 2:54 AM Lidong Dai wrote:
>
>> +1 to retire
>>
>> Best Regards
>>
>>
>>
>> ---
>> Apache
Dear IPMC:
Due to the suggestion in [1], I have to cancel this vote to address the
following issue:
1. Change the name of artifact to following the naming rule of scala.
Thank you all for your time.
[1] https://lists.apache.org/thread/l8oh5xmf07vjp1nd50qmo59wmf8zstj2
--
此致！Best Regards
Dear IPMC:
Due to the suggestion in [1], I have to cancel this vote to address the
following issue:
1. Change the name of artifact to following the naming rule of scala.
[1] https://lists.apache.org/thread/l8oh5xmf07vjp1nd50qmo59wmf8zstj2
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
Thank you so much!
We will change name of artifacts to follow the naming rules.
And this vote will be cancelled.
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmin...@apache.org
At 2022-03-05 20:55:29, "Cheng Pan" wrote:
>BTW, there are other examples and I think they can help you to
+1 (binding)
I have checked the following items:
- Incubating in name
- LICENSE and NOTICE are fine
- DISCLAIMER exists
- No unexpected binary files
- All ASF files have ASF headers
Xun Liu
Best Regards,
On Sat, Mar 5, 2022 at 5:47 PM Lior Schachter wrote:
> Thank you Xun & sebb. I applied
BTW, there are other examples and I think they can help you to think
about how to name your project components.
1. spark-cassandra-connector_2.12[1], does not make the spark minor
version be part of the artifact name, but documents the support
matrix[2] instead.
2. elasticsearch-spark-20_2.12[3],
Usually Spark keeps good binary compatibility in the same minor
versions, it says that the downstream project builds against spark
3.1.2 is also expected to work with spark 3.1.3, but not spark 3.2.x,
so, it's rare to keep a patch version in the name.
I think Apache Iceberg does a good job in this
Hi Cheng Pan:
Thanks for the reminder, I didn't know there was such a rule before.
Our current version names are:
doris-spark-connector-3.1.2-2.12-1.0.0
Among them, 3.1.2 is the spark version, 2.12 is the scala version, and 1.0.0 is
the version of the connector itself.
What we need to do is
Thank you Xun & sebb. I applied your suggested fix.
https://downloads.apache.org/incubator/liminal/KEYS is now the only source
for the project's KEYS.
We need an extra +1 (binding) to complete the vote.
Regards,
Lior
On Thu, Mar 3, 2022 at 3:18 AM Xun Liu wrote:
> Hi, Lior Schachter
>
> As
+1
I have verified the checkability below??
[x] Is the download link legal?
[x] Check whether the value and PGP signature are legal.
[x] Whether to include a DISCLAIMER or DISCLAIMER-WIP file.
[x] Whether the code matches the current release version.
[x] LICENSE and NOTICE files are correct.
Hi,
One question about the name of artifacts, it seems does not follow the
common practice, the recommended artifact name pattern is
"{aritifact_name}_{scala_binary_version}", e.g. `spark-core_2.12`,
this is the default behavior defined in sbt[1] and the de facto
artifact name pattern in scala
12 matches
Mail list logo
