[VOTE] Release Apache Pegasus (Incubating) 2.5.0 [RC1]
Hello all, This is a call for a vote to release Apache Pegasus (Incubating) version 2.5.0. The Apache Pegasus community has voted on and approved a proposal to release Apache Pegasus (Incubating) version 2.5.0. We now kindly request the Incubator PMC members review and vote on this incubator release. Apache Pegasus is a distributed key-value storage system that is designed to be simple, horizontally scalable, strongly consistent, and high-performance. Apache Pegasus community vote and result thread: Vote: https://lists.apache.org/thread/ob0h55oq9yr0d77czprftw24wwx2xchr Result: https://lists.apache.org/thread/p54269djfbwgllwp7trj0c12x07w4xp8 The source tarball, including signatures, digests, etc. can be found at: https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.5.0-RC1/ It is tagged in Git as v2.5.0-RC1 on Github: https://github.com/apache/incubator-pegasus/tree/v2.5.0-RC1 The corresponding hash is the following: https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=0ca31b70eac7321bb17fb034105695597245d47b For information about the contents of this release, see release notes: https://github.com/apache/incubator-pegasus/blob/50563ea33b33c5ae1a6d9b8e4cf74a7d1d9133b0/HISTORY.md The artifacts have been signed with Key : 8041A06E53E4312A, which can be found in KEYS file: https://downloads.apache.org/incubator/pegasus/KEYS Look at here for how to verify this release candidate: https://cwiki.apache.org/confluence/display/PEGASUS/Validating+a+staged+release The vote will be open for at least 72 hours or until the necessary number of votes are reached. Please vote accordingly: [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove with the reason Best regards, Dan Wang
December Podling reports
Hi everyone, Just in case, things seem a little behind with the setup of the podling reporting for December (i.e. the cwiki page hasn't been setup). It looks like these podlings need to report based on having reported in September. Baremaps KIE Liminal Nemo Uniffle Wayang These 3 failed to report last month and should report for next month. Livy Ponymail Teaclave All 3 same to be a few months late. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] HoraeDB proposal
Hi IPMC,
Is there any concern left before initializing the vote? I hope we have
addressed most before the start.
I can see the HoraeDB project is open to learning more about the
ASF culture in the incubating process. And they do react to the
comments above and take action.
It is not perfect and fully compatible with ASF yet - this is the point
of the whole incubating.
Best,
tison.
Jiacai Liu 于2023年11月30日周四 16:24写道：
>
>
> Hi,
>
> Yingwen is one of the core early developers of the project, if you
> execute `git grep yingwen`, you could see lots of comments written
> by him.
> However when we open source horaedb on GitHub, we do a git stash
> to make the git history clean, so you couldn't see his commit
> anymore.
>
> Now he isn't working in AntGroup anymore, but since he contributed
> significantly to the early stages of development, so we list him
> under initial committers.
>
> On Wed, Nov 29, 2023 at 06:13:42 PM +0800, Yu Xiao wrote:
>
> > Hi，
> >
> > I checked the list of contributors[1], not find initial
> > Committers
> > for Yingwen Yang(GitHub ID = evenyag) .
> >
> > [1] https://github.com/CeresDB/horaedb/graphs/contributors
> >
> > Best wishes!
> >
> > tison 于2023年11月29日周三 15:55写道：
> >>
> >> > You also have things like this, which was published in the
> >> > last day. If the name has changed,
> >> > why is this still being published under the old name?
> >> > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
> >>
> >> If your cornern for asking permission for use CeresDB trademark
> >> is due
> >> to the existing usage, we can evaluate and choose either way:
> >>
> >> 1. Rename all the artifacts before entering the incubator.
> >> 2. Ask for Ant Group to grant a permission to use CeresDB
> >> trademark
> >> for such legacy code reference.
> >>
> >> Does this make sense and your concern point?
> >>
> >> Anyway, we will stop releasing new artifacts with the name
> >> CeresDB as
> >> prioritize the renaming task.
> >>
> >> Best,
> >> tison.
> >>
> >> tison 于2023年11月29日周三 15:45写道：
> >> >
> >> > > The proposal doesn't address these naming issues; please
> >> > > update it to include how these will
> >> > > be handled. All of the changes don't need to happen before
> >> > > donation, just meantion how they
> >> > > will be handled, but you do need to respect 3rd party
> >> > > trademarks.
> >> >
> >> > Thanks for your reply. This is tracked in [1] and we will
> >> > elaborate
> >> > the actions and integrate it in the proposal. Renaming
> >> > code/text is
> >> > happening so the references will be reduced down.
> >> >
> >> > > My previous question regards whether the project has been
> >> > > given permission to use the CeresDB
> >> > > trademark has still not been answered.
> >> > >> So it's not an issue that -
> >> > >>> Has the company given permission to use their trademark?
> >> > >> No or N/A. The HoraeDB website won't use CeresDB
> >> > >> trademarks.
> >> > >>> If so, how is it allowed to be used? This should be
> >> > >>> included in the proposal.
> >> > >>N/A
> >> >
> >> > So the answer for "whether" is no for no need.
> >> >
> >> > Best,
> >> > tison.
> >> >
> >> > [1] https://github.com/CeresDB/horaedb/issues/1319
> >> >
> >> > Justin Mclean 于2023年11月29日周三
> >> > 15:34写道：
> >> > >
> >> > > HI,
> >> > >
> >> > > > project still wants to use the CeresDB name in some
> >> > > > form. Is this correct
> >> > > > or not?
> >> > > > NO.
> >> > >
> >> > > Then why does the code in the code still refer to CeresDB
> >> > > in 100+ places?
> >> > >
> >> > > for instance, the source path is:
> >> > > /horaedb/src/ceresdb
> >> > >
> >> > > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it
> >> > > contains things like:
> >> > > const NODE_ADDR: = "CERESDB_SERVER_ADDR”;
> >> > > use ceresdb:
> >> > > println!("CeresDB server tries starting with
> >> > > config:{config:?}”);
> >> > >
> >> > > in src/ceresdb/Cargo.toml
> >> > > [package]
> >> > > name = "ceresdb"
> >> > >
> >> > > Dockerfile
> >> > > COPY . /ceresdb
> >> > > WORKDIR /ceresdb## CeresDBCOPY --from=build
> >> > > /ceresdb/target/release/ceresdb-server
> >> > > /usr/bin/ceresdb-server
> >> > > RUN chmod +x /usr/bin/ceresdb-serverCOPY
> >> > > ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
> >> > >
> >> > > And as mentioned, 100+ other instances.
> >> > >
> >> > > You also have things like this, which was published in the
> >> > > last day. If the name has changed,
> >> > > why is this still being published under the old name?
> >> > > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
> >> > >
> >> > > The proposal doesn't address these naming issues; please
> >> > > update it to include how these will
> >> > > be handled. All of the changes don't need to happen before
> >> > > donation, just meantion how they
> >> > > will be handled, but you do need to respect 3rd party
> >> > > trademarks.
> >> > >
> >> > > My previous question regards whether the project has been
> >> > > given permission to use
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
Thanks PJ and Yu, This RC has been cancelled. We will: 1. exclude JindoData dependency. 2. move paimon-plugin-s3/META-INF to /META-INF Best, Jingsong On Thu, Nov 30, 2023 at 6:31 PM Yu Li wrote: > > -1 (binding) > > When checking the diff between 0.5.0 and 0.6.0 [1] I noticed newly introduced > dependency on JindoData [2] [3], which is not open sourced (binary and docs > only in the github repo) and has the risk to bundle codes with unapproved > licenses. > > Best Regards, > Yu > > [1] > https://github.com/apache/incubator-paimon/compare/release-0.5.0-incubating...release-0.6.0-incubating-rc1 > [2] https://github.com/apache/incubator-paimon/pull/2290 > [3] https://github.com/aliyun/alibabacloud-jindodata > > > On Wed, 29 Nov 2023 at 10:30, Jingsong Li wrote: >> >> Hi PJ and Yu, >> >> Thanks for the careful checking and suggestions. I've opened [1] to >> track the issue and we will resolve it in the next release, if you >> also don't think this is a release blocker. >> >> [1] https://github.com/apache/incubator-paimon/issues/2413 >> >> Best, >> Jingsong >> >> On Wed, Nov 29, 2023 at 8:33 AM Yu Li wrote: >> > >> > I agree that the current organization of the jar is a little bit >> > confusing. It would be better to keep a single META-INF directory at the >> > root level, and introduce no additional "paimon-plugin-s3" directory in >> > the dir tree. >> > >> > @Jingsong Li and team: please take a look here and open an issue to >> > track/resolve it if you also find this reasonable, or let us know your >> > thoughts if I miss anything. >> > >> > Best Regards, >> > Yu >> > >> > >> > On Wed, 29 Nov 2023 at 03:08, PJ Fanning wrote: >> >> >> >> I've also never seen the multi-release classes in a dir like >> >> paimon-plugin-s3/META-INF/versions/ - I've only ever seen them in >> >> META-INF/versions dir (ie no paimon-plugin-s3 dir in the dir tree). >> >> >> >> On Tue, 28 Nov 2023 at 20:03, PJ Fanning wrote: >> >> > >> >> > Why is there a META-INF dir and a paimon-plugin-s3/META-INF dir with >> >> > revival license files? >> >> > >> >> > I must admit to finding this confusing. Is there any way to only have >> >> > one META-INF dir. Most people expect META-INF at the root level - so >> >> > if we consolidate the 2 META-INF dirs then I'd prefer if the root >> >> > level one is the one that is kept. >> >> > >> >> > On Tue, 28 Nov 2023 at 15:50, Yu Li wrote: >> >> > > >> >> > > Hi PJ, >> >> > > >> >> > > Thanks for the notice. >> >> > > >> >> > > It seems to me that in the META-INF/NOTICE file bundled in the >> >> > > paimon-s3-0.6.0-incubating.jar files, there're license disclaimers >> >> > > about >> >> > > the dependencies, with references to the location of the relative >> >> > > license >> >> > > file (under the nested "licenses" directory), such as: >> >> > > - >> >> > > >> >> > > This project bundles the following dependencies under BSD-2 License ( >> >> > > https://opensource.org/licenses/BSD-2-Clause). >> >> > > >> >> > > You find it under licenses/LICENSE.dnsjava. >> >> > > >> >> > > ... >> >> > > >> >> > > This project bundles the following dependencies under the MIT ( >> >> > > https://opensource.org/licenses/MIT) >> >> > > >> >> > > You find them under licenses/LICENSE.checker-framework-qualifiers and >> >> > > licenses/LICENSE.animal-sniffer. >> >> > > >> >> > > ... >> >> > > >> >> > > This project bundles the following dependencies under the CDDL 1.1 >> >> > > license. >> >> > > >> >> > > You find it under licenses/LICENSE.jaxb. >> >> > > >> >> > > ... >> >> > > - >> >> > > >> >> > > I happen to know this since I noticed similar issues and asked the >> >> > > team to >> >> > > resolve them in release 0.4.0 [1], so just for your information. >> >> > > >> >> > > Since I haven't completed checking this rc yet, it's possible that >> >> > > there >> >> > > are newly introduced dependencies in the paimon-filesystems module >> >> > > (especially the paimon-s3 and paimon-s3-impl sub-modules). Would you >> >> > > mind >> >> > > further checking it and let us know the detailed dependency with >> >> > > license >> >> > > (notice/file) missing? Thanks. >> >> > > >> >> > > And I will also check this carefully when time allows. >> >> > > >> >> > > Best Regards, >> >> > > Yu >> >> > > >> >> > > [1] >> >> > > https://github.com/apache/incubator-paimon/pull/1067#issuecomment-1537338118 >> >> > > >> >> > > On Tue, 28 Nov 2023 at 18:10, PJ Fanning wrote: >> >> > > >> >> > > > There is a META-INF/DEPENDENCIES file in >> >> > > > paimon-s3-0.6.0-incubating.jar but it lists only a small fraction of >> >> > > > the external jars that are bundled into >> >> > > > paimon-s3-0.6.0-incubating.jar. >> >> > > > >> >> > > > On Tue, 28 Nov 2023 at 11:05, PJ Fanning >> >> > > > wrote: >> >> > > > > >> >> > > > > I had a look at this jar: >> >> > > > > >> >> > > > > >> >> > > >
Re: [VOTE] Release Apache Paimon(incubating) 0.6.0-incubating rc1
-1 (binding) When checking the diff between 0.5.0 and 0.6.0 [1] I noticed newly introduced dependency on JindoData [2] [3], which is not open sourced (binary and docs only in the github repo) and has the risk to bundle codes with unapproved licenses. Best Regards, Yu [1] https://github.com/apache/incubator-paimon/compare/release-0.5.0-incubating...release-0.6.0-incubating-rc1 [2] https://github.com/apache/incubator-paimon/pull/2290 [3] https://github.com/aliyun/alibabacloud-jindodata On Wed, 29 Nov 2023 at 10:30, Jingsong Li wrote: > Hi PJ and Yu, > > Thanks for the careful checking and suggestions. I've opened [1] to > track the issue and we will resolve it in the next release, if you > also don't think this is a release blocker. > > [1] https://github.com/apache/incubator-paimon/issues/2413 > > Best, > Jingsong > > On Wed, Nov 29, 2023 at 8:33 AM Yu Li wrote: > > > > I agree that the current organization of the jar is a little bit > confusing. It would be better to keep a single META-INF directory at the > root level, and introduce no additional "paimon-plugin-s3" directory in the > dir tree. > > > > @Jingsong Li and team: please take a look here and open an issue to > track/resolve it if you also find this reasonable, or let us know your > thoughts if I miss anything. > > > > Best Regards, > > Yu > > > > > > On Wed, 29 Nov 2023 at 03:08, PJ Fanning wrote: > >> > >> I've also never seen the multi-release classes in a dir like > >> paimon-plugin-s3/META-INF/versions/ - I've only ever seen them in > >> META-INF/versions dir (ie no paimon-plugin-s3 dir in the dir tree). > >> > >> On Tue, 28 Nov 2023 at 20:03, PJ Fanning wrote: > >> > > >> > Why is there a META-INF dir and a paimon-plugin-s3/META-INF dir with > >> > revival license files? > >> > > >> > I must admit to finding this confusing. Is there any way to only have > >> > one META-INF dir. Most people expect META-INF at the root level - so > >> > if we consolidate the 2 META-INF dirs then I'd prefer if the root > >> > level one is the one that is kept. > >> > > >> > On Tue, 28 Nov 2023 at 15:50, Yu Li wrote: > >> > > > >> > > Hi PJ, > >> > > > >> > > Thanks for the notice. > >> > > > >> > > It seems to me that in the META-INF/NOTICE file bundled in the > >> > > paimon-s3-0.6.0-incubating.jar files, there're license disclaimers > about > >> > > the dependencies, with references to the location of the relative > license > >> > > file (under the nested "licenses" directory), such as: > >> > > - > >> > > > >> > > This project bundles the following dependencies under BSD-2 License > ( > >> > > https://opensource.org/licenses/BSD-2-Clause). > >> > > > >> > > You find it under licenses/LICENSE.dnsjava. > >> > > > >> > > ... > >> > > > >> > > This project bundles the following dependencies under the MIT ( > >> > > https://opensource.org/licenses/MIT) > >> > > > >> > > You find them under licenses/LICENSE.checker-framework-qualifiers > and > >> > > licenses/LICENSE.animal-sniffer. > >> > > > >> > > ... > >> > > > >> > > This project bundles the following dependencies under the CDDL 1.1 > license. > >> > > > >> > > You find it under licenses/LICENSE.jaxb. > >> > > > >> > > ... > >> > > - > >> > > > >> > > I happen to know this since I noticed similar issues and asked the > team to > >> > > resolve them in release 0.4.0 [1], so just for your information. > >> > > > >> > > Since I haven't completed checking this rc yet, it's possible that > there > >> > > are newly introduced dependencies in the paimon-filesystems module > >> > > (especially the paimon-s3 and paimon-s3-impl sub-modules). Would > you mind > >> > > further checking it and let us know the detailed dependency with > license > >> > > (notice/file) missing? Thanks. > >> > > > >> > > And I will also check this carefully when time allows. > >> > > > >> > > Best Regards, > >> > > Yu > >> > > > >> > > [1] > >> > > > https://github.com/apache/incubator-paimon/pull/1067#issuecomment-1537338118 > >> > > > >> > > On Tue, 28 Nov 2023 at 18:10, PJ Fanning > wrote: > >> > > > >> > > > There is a META-INF/DEPENDENCIES file in > >> > > > paimon-s3-0.6.0-incubating.jar but it lists only a small fraction > of > >> > > > the external jars that are bundled into > >> > > > paimon-s3-0.6.0-incubating.jar. > >> > > > > >> > > > On Tue, 28 Nov 2023 at 11:05, PJ Fanning > wrote: > >> > > > > > >> > > > > I had a look at this jar: > >> > > > > > >> > > > > > >> > > > > https://repository.apache.org/content/repositories/orgapachepaimon-1029/org/apache/paimon/paimon-s3/0.6.0-incubating/paimon-s3-0.6.0-incubating.jar > >> > > > > > >> > > > > It has a META-INF/LICENSE file but this file is a generic ASF > license > >> > > > > and has no details about all the non-ASF classes that are > bundled in > >> > > > > the jar. > >> > > > > > >> > > > > The META-INF/NOTICE likewise does not mention anything about the > >> > > > > non-ASF classes. > >> > > > > > >> > > > > > >> > > > > On Mon, 27 Nov
Re: [DISCUSS] HoraeDB proposal
Hi,
Yingwen is one of the core early developers of the project, if you
execute `git grep yingwen`, you could see lots of comments written
by him.
However when we open source horaedb on GitHub, we do a git stash
to make the git history clean, so you couldn't see his commit
anymore.
Now he isn't working in AntGroup anymore, but since he contributed
significantly to the early stages of development, so we list him
under initial committers.
On Wed, Nov 29, 2023 at 06:13:42 PM +0800, Yu Xiao wrote:
Hi，
I checked the list of contributors[1], not find initial
Committers
for Yingwen Yang(GitHub ID = evenyag) .
[1] https://github.com/CeresDB/horaedb/graphs/contributors
Best wishes!
tison 于2023年11月29日周三 15:55写道：
> You also have things like this, which was published in the
> last day. If the name has changed,
> why is this still being published under the old name?
> https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
If your cornern for asking permission for use CeresDB trademark
is due
to the existing usage, we can evaluate and choose either way:
1. Rename all the artifacts before entering the incubator.
2. Ask for Ant Group to grant a permission to use CeresDB
trademark
for such legacy code reference.
Does this make sense and your concern point?
Anyway, we will stop releasing new artifacts with the name
CeresDB as
prioritize the renaming task.
Best,
tison.
tison 于2023年11月29日周三 15:45写道：
>
> > The proposal doesn't address these naming issues; please
> > update it to include how these will
> > be handled. All of the changes don't need to happen before
> > donation, just meantion how they
> > will be handled, but you do need to respect 3rd party
> > trademarks.
>
> Thanks for your reply. This is tracked in [1] and we will
> elaborate
> the actions and integrate it in the proposal. Renaming
> code/text is
> happening so the references will be reduced down.
>
> > My previous question regards whether the project has been
> > given permission to use the CeresDB
> > trademark has still not been answered.
> >> So it's not an issue that -
> >>> Has the company given permission to use their trademark?
> >> No or N/A. The HoraeDB website won't use CeresDB
> >> trademarks.
> >>> If so, how is it allowed to be used? This should be
> >>> included in the proposal.
> >>N/A
>
> So the answer for "whether" is no for no need.
>
> Best,
> tison.
>
> [1] https://github.com/CeresDB/horaedb/issues/1319
>
> Justin Mclean 于2023年11月29日周三
> 15:34写道：
> >
> > HI,
> >
> > > project still wants to use the CeresDB name in some
> > > form. Is this correct
> > > or not?
> > > NO.
> >
> > Then why does the code in the code still refer to CeresDB
> > in 100+ places?
> >
> > for instance, the source path is:
> > /horaedb/src/ceresdb
> >
> > looking at horaedbsrc/ceresdb/bin/ceresdb-server.rs it
> > contains things like:
> > const NODE_ADDR: = "CERESDB_SERVER_ADDR”;
> > use ceresdb:
> > println!("CeresDB server tries starting with
> > config:{config:?}”);
> >
> > in src/ceresdb/Cargo.toml
> > [package]
> > name = "ceresdb"
> >
> > Dockerfile
> > COPY . /ceresdb
> > WORKDIR /ceresdb## CeresDBCOPY --from=build
> > /ceresdb/target/release/ceresdb-server
> > /usr/bin/ceresdb-server
> > RUN chmod +x /usr/bin/ceresdb-serverCOPY
> > ./docs/minimal.toml /etc/ceresdb/ceresdb.toml
> >
> > And as mentioned, 100+ other instances.
> >
> > You also have things like this, which was published in the
> > last day. If the name has changed,
> > why is this still being published under the old name?
> > https://github.com/CeresDB/horaedb/pkgs/container/ceresdb-server
> >
> > The proposal doesn't address these naming issues; please
> > update it to include how these will
> > be handled. All of the changes don't need to happen before
> > donation, just meantion how they
> > will be handled, but you do need to respect 3rd party
> > trademarks.
> >
> > My previous question regards whether the project has been
> > given permission to use the CeresDB
> > trademark has still not been answered.
> >
> > Kind Regards,
> > Justin
> > -
> > To unsubscribe, e-mail:
> > general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail:
> > general-h...@incubator.apache.org
> >
-
To unsubscribe, e-mail:
general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
general-h...@incubator.apache.org
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
