Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
PragmaTwice commented on PR #1643: URL: https://github.com/apache/incubator-fury/pull/1643#issuecomment-2120439938 > > > @PragmaTwice What we do here is like the method you proposed in `create the branch from the dev branch after we decide to release 0.5.1`. But I think we can switch to release branch `a.b` instead of `a.b.c`. > > > > > > I see. Seems now the release procedure is cancelled so maybe we can just delete the old branch and create a new. > > It's protected branch, we can't delete it https://github.com/apache/incubator-fury/blob/main/.asf.yaml seems not protected? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
svn commit: r69290 - in /dev/incubator/fury/0.5.1-rc2: ./ apache-fury-0.5.1-incubating-src.tar.gz apache-fury-0.5.1-incubating-src.tar.gz.asc apache-fury-0.5.1-incubating-src.tar.gz.sha512
Author: chaokunyang Date: Mon May 20 09:55:44 2024 New Revision: 69290 Log: Prepare for fury 0.5.1-rc2 Added: dev/incubator/fury/0.5.1-rc2/ dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz (with props) dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.asc dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.sha512 Added: dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz == Binary file - no diff available. Propchange: dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz -- svn:mime-type = application/octet-stream Added: dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.asc == --- dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.asc (added) +++ dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.asc Mon May 20 09:55:44 2024 @@ -0,0 +1,16 @@ +-BEGIN PGP SIGNATURE- + +iQIzBAABCAAdFiEEHiza5MCK19aU0csTnXvo5F5YC6QFAmZLHKcACgkQnXvo5F5Y +C6RKuQ/+K+n5cACQTEeP7HXizsqsUYtKJIjWwMH/2+/g5MzZRekWSeXdVqNx4u3f +dHWKv6Hic7PNkEm1IErFAHH2GAsOJy/Mj7ANLUUFvPQEGqvB2b5MkSAzGtOD7NDR +Gsn7+C350iUkaVKXeqY0hunS7Ynd9+zGW2MgUREczOdmCfDV+7+1kiVZTkcmFYX8 +RBZnNdy6X/GE1oXx0xGzkOfdeS0UZUwlmdZZOA/W3qOBKcqXsK0cGT8NIYB8XLwh +lxTN35irQ+KQyu8mwtUfmJXPbxTWcJpYg2KUW1t3qcitnUsjJa03UrlGroI49WgM +Tuwcwsdw+Ncqmg4rb0QVw0P63SxBo4nXOcG3o23i+txGjlXpAXrYzzJNParxCb+2 +v4zAIVInGd1EPZ/kQqRUr7uxjt0t7f/2LBS12dpdmCrlEtUSGHBjTjGn8C2U/ROr +LMdhF9uISWhEzFu9z70vRyJPxcP84D+TBsc9nAQykHI7tyzvCoNoNIlPzklzElSI +b4mXleQPxLCECFrThbFQlqLUo60goMFppjZO/b9UWGw6bjiIQ3zBvbKzzMBHqlbF +YmMUbL91ez1yJaBYfxsk57QnSzukQQ/0uCb0ijCzXZH8TQyqZICeoVDDV2soeOwK +Rshj663aE+kJcSgatwmSEECppPk7gBMJDOymchfJcz7h3Lx62m0= +=J1wL +-END PGP SIGNATURE- Added: dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.sha512 == --- dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.sha512 (added) +++ dev/incubator/fury/0.5.1-rc2/apache-fury-0.5.1-incubating-src.tar.gz.sha512 Mon May 20 09:55:44 2024 @@ -0,0 +1 @@ +593bb6c9fadfe84f6ace02157563bad671398507d9faa999aed1de7938522440f4bf1a65ee0db489fb894f9a25c7dab82fa5dceac0b9b583bc7150f86a8e85fe apache-fury-0.5.1-incubating-src.tar.gz - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
(incubator-fury) tag v0.5.1-rc2 created (now 0455ff73)
This is an automated email from the ASF dual-hosted git repository. chaokunyang pushed a change to tag v0.5.1-rc2 in repository https://gitbox.apache.org/repos/asf/incubator-fury.git at 0455ff73 (commit) This tag includes the following new commits: new 0455ff73 prepare release for 0.5.1 The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
(incubator-fury) 01/01: prepare release for 0.5.1
This is an automated email from the ASF dual-hosted git repository.
chaokunyang pushed a commit to tag v0.5.1-rc2
in repository https://gitbox.apache.org/repos/asf/incubator-fury.git
commit 0455ff732b9217785193f8e45f3a013eb5539e46
Author: chaokunyang
AuthorDate: Mon May 20 17:45:30 2024 +0800
prepare release for 0.5.1
---
.github/workflows/release.yaml| 4 ++--
integration_tests/graalvm_tests/pom.xml | 2 +-
integration_tests/jdk_compatibility_tests/pom.xml | 2 +-
integration_tests/jpms_tests/pom.xml | 2 +-
integration_tests/latest_jdk_tests/pom.xml| 2 +-
java/benchmark/pom.xml| 2 +-
java/fury-core/pom.xml| 2 +-
java/fury-format/pom.xml | 2 +-
java/fury-test-core/pom.xml | 2 +-
java/fury-testsuite/pom.xml | 2 +-
java/pom.xml | 2 +-
javascript/packages/fury/package.json | 2 +-
javascript/packages/hps/package.json | 2 +-
rust/Cargo.toml | 2 +-
scala/build.sbt | 2 +-
15 files changed, 16 insertions(+), 16 deletions(-)
diff --git a/.github/workflows/release.yaml b/.github/workflows/release.yaml
index b1d5fd81..117922cc 100644
--- a/.github/workflows/release.yaml
+++ b/.github/workflows/release.yaml
@@ -20,7 +20,7 @@ name: Publish Fury
on:
push:
tags:
- - 'v*'
+ - 'disabled*'
jobs:
release-python:
@@ -43,7 +43,7 @@ jobs:
run: ./ci/run_ci.sh install_bazel
- name: Update version in setup.py
run: |
- echo "GITHUB_REF: $GITHUB_REF"
+ echo "GITHUB_REF: $GITHUB_REF"
tag=$(echo $GITHUB_REF | cut -d / -f 3)
echo "tag: $tag"
version=${tag:1}
diff --git a/integration_tests/graalvm_tests/pom.xml
b/integration_tests/graalvm_tests/pom.xml
index d3f952c2..44e8cd61 100644
--- a/integration_tests/graalvm_tests/pom.xml
+++ b/integration_tests/graalvm_tests/pom.xml
@@ -25,7 +25,7 @@
org.apache.fury
fury-parent
-0.6.0-SNAPSHOT
+0.5.1
../../java
4.0.0
diff --git a/integration_tests/jdk_compatibility_tests/pom.xml
b/integration_tests/jdk_compatibility_tests/pom.xml
index f6af0074..238fc7cc 100644
--- a/integration_tests/jdk_compatibility_tests/pom.xml
+++ b/integration_tests/jdk_compatibility_tests/pom.xml
@@ -25,7 +25,7 @@
org.apache.fury
fury-parent
-0.6.0-SNAPSHOT
+0.5.1
../../java
4.0.0
diff --git a/integration_tests/jpms_tests/pom.xml
b/integration_tests/jpms_tests/pom.xml
index fca2007f..3744a267 100644
--- a/integration_tests/jpms_tests/pom.xml
+++ b/integration_tests/jpms_tests/pom.xml
@@ -25,7 +25,7 @@
org.apache.fury
fury-parent
-0.6.0-SNAPSHOT
+0.5.1
../../java
4.0.0
diff --git a/integration_tests/latest_jdk_tests/pom.xml
b/integration_tests/latest_jdk_tests/pom.xml
index 015633ec..a7852650 100644
--- a/integration_tests/latest_jdk_tests/pom.xml
+++ b/integration_tests/latest_jdk_tests/pom.xml
@@ -25,7 +25,7 @@
org.apache.fury
fury-parent
-0.6.0-SNAPSHOT
+0.5.1
../../java
4.0.0
diff --git a/java/benchmark/pom.xml b/java/benchmark/pom.xml
index 89a2cb6a..e7ab6b47 100644
--- a/java/benchmark/pom.xml
+++ b/java/benchmark/pom.xml
@@ -26,7 +26,7 @@
fury-parent
org.apache.fury
-0.6.0-SNAPSHOT
+0.5.1
benchmark
diff --git a/java/fury-core/pom.xml b/java/fury-core/pom.xml
index dcf87204..c2aad443 100644
--- a/java/fury-core/pom.xml
+++ b/java/fury-core/pom.xml
@@ -25,7 +25,7 @@
org.apache.fury
fury-parent
-0.6.0-SNAPSHOT
+0.5.1
4.0.0
diff --git a/java/fury-format/pom.xml b/java/fury-format/pom.xml
index 6c4c6cb6..33500a81 100644
--- a/java/fury-format/pom.xml
+++ b/java/fury-format/pom.xml
@@ -25,7 +25,7 @@
org.apache.fury
fury-parent
-0.6.0-SNAPSHOT
+0.5.1
4.0.0
diff --git a/java/fury-test-core/pom.xml b/java/fury-test-core/pom.xml
index b129d1ca..191e348c 100644
--- a/java/fury-test-core/pom.xml
+++ b/java/fury-test-core/pom.xml
@@ -25,7 +25,7 @@
fury-parent
org.apache.fury
-0.6.0-SNAPSHOT
+0.5.1
4.0.0
diff --git a/java/fury-testsuite/pom.xml b/java/fury-testsuite/pom.xml
index 165e17db..516a90a5 100644
--- a/java/fury-testsuite/pom.xml
+++ b/java/fury-testsuite/pom.xml
@@ -25,7 +25,7 @@
fury-parent
org.apache.fury
-0.6.0-SNAPSHOT
+0.5.1
4.0.0
diff --git a/java/pom.xml b/java/pom.xml
index 9fec9525..0cdd2346 100644
--- a/java/pom.xml
+++ b/java/pom.xml
@@ -33,7 +33,7 @@
org.apache.fury
fury-parent
pom
- 0.6.0-SNAPSHOT
+ 0.5.1
Fury Project Parent POM
Apache Fury™ is a blazingly fast multi-language serialization framework
powered by jit and zero-copy.
diff --git a/javascript/packages/fury/packa
(incubator-fury) tag v0.5.1-rc2 deleted (was 179f9e6e)
This is an automated email from the ASF dual-hosted git repository. chaokunyang pushed a change to tag v0.5.1-rc2 in repository https://gitbox.apache.org/repos/asf/incubator-fury.git *** WARNING: tag v0.5.1-rc2 was deleted! *** was 179f9e6e bump version to 0.5.1 The revisions that were on this tag are still contained in other references; therefore, this change does not discard any commits from the repository. - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
chaokunyang commented on PR #1643: URL: https://github.com/apache/incubator-fury/pull/1643#issuecomment-2120058852 > > @PragmaTwice What we do here is like the method you proposed in `create the branch from the dev branch after we decide to release 0.5.1`. But I think we can switch to release branch `a.b` instead of `a.b.c`. > > I see. Seems now the release procedure is cancelled so maybe we can just delete the old branch and create a new. It's protected branch, we can't delete it -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
PragmaTwice commented on PR #1643: URL: https://github.com/apache/incubator-fury/pull/1643#issuecomment-2120056276 > @PragmaTwice What we do here is like the method you proposed in `create the branch from the dev branch after we decide to release 0.5.1`. But I think we can switch to release branch `a.b` instead of `a.b.c`. I see. Seems now the release procedure is cancelled so maybe we can just delete the old branch and create a new. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
[GH] (incubator-fury): Workflow run "Publish Fury" failed!
The GitHub Actions job "Publish Fury" on incubator-fury.git has failed. Run started by GitHub user chaokunyang (triggered by chaokunyang). Head commit for run: 179f9e6ec82f67f909e915d96744767344cba034 / chaokunyang bump version to 0.5.1 Report URL: https://github.com/apache/incubator-fury/actions/runs/9156277895 With regards, GitHub Actions via GitBox - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
(incubator-fury) tag v0.5.1-rc2 created (now 179f9e6e)
This is an automated email from the ASF dual-hosted git repository. chaokunyang pushed a change to tag v0.5.1-rc2 in repository https://gitbox.apache.org/repos/asf/incubator-fury.git at 179f9e6e (commit) No new revisions were added by this update. - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
(incubator-fury) branch releases-0.5 created (now 03dba113)
This is an automated email from the ASF dual-hosted git repository. chaokunyang pushed a change to branch releases-0.5 in repository https://gitbox.apache.org/repos/asf/incubator-fury.git at 03dba113 feat(java): remove soft/weak ref values from thread safe fury (#1639) No new revisions were added by this update. - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
chaokunyang commented on PR #1643: URL: https://github.com/apache/incubator-fury/pull/1643#issuecomment-211909 @PragmaTwice What we do here is like the method you proposed in `create the branch from the dev branch after we decide to release 0.5.1`. But I think we can switch to release branch `a.b` instead of `a.b.c`. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
chaokunyang closed pull request #1643: chore: merge main into 0.5.1 URL: https://github.com/apache/incubator-fury/pull/1643 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
chaokunyang commented on PR #1643: URL: https://github.com/apache/incubator-fury/pull/1643#issuecomment-2119931780 > Hmmm I have a little question about branching and release management. > > It seems a little weird to merge something to a release branch continuously. Maybe we can just create the branch from the dev branch after we decide to release 0.5.1? Or maybe we can maintain a branch named `release-0.5`, and use it to create release tag (0.5.1, 0.5.2...) if there are some inconsistencies between release branch and the dev branch? (e.g. follow the semantic versioning) The 0.5.1 has been created from dev branch before, we can't overwrite it. Using cherry-pick is better actually. The dev branch didn't introduce big changes so I just created a PR to merge code from dev branch. Currently I create release candidate tag from release branch `release-a.b.c`, for example: create tag 0.5.1-rc2 from branch releases-0.5.1. Creating tag from ``release-a.b` looks to me too. I will do that -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
PragmaTwice commented on PR #1643: URL: https://github.com/apache/incubator-fury/pull/1643#issuecomment-2119835430 Hmmm I have a little question about branching and release management. It seems a little weird to merge something to a release branch continuously. Maybe we can just create the branch from the dev branch after we decide to release 0.5.1? Or maybe we can maintain a branch named `release-0.5`, and use it to create release tag if there are some inconsistencies between release branch and the dev branch? (e.g. follow the semantic versioning) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
[PR] chore: merge main into 0.5.1 [incubator-fury]
chaokunyang opened a new pull request, #1643: URL: https://github.com/apache/incubator-fury/pull/1643 ## What does this PR do? ## Related issues ## Does this PR introduce any user-facing change? - [ ] Does this PR introduce any public API change? - [ ] Does this PR introduce any binary protocol compatibility change? ## Benchmark -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] feat(java): remove soft/weak ref values from thread safe fury [incubator-fury]
chaokunyang commented on PR #1639: URL: https://github.com/apache/incubator-fury/pull/1639#issuecomment-2119817838 Yep, this is a smaller dependency. Fury is a low-level library, we want to make a zero-dependency in the long time. The cache usage in Fury is very simple. Maybe we can implement it manually too. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] chore: merge main into 0.5.1 [incubator-fury]
chaokunyang closed pull request #1642: chore: merge main into 0.5.1 URL: https://github.com/apache/incubator-fury/pull/1642 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
[PR] chore: merge main into 0.5.1 [incubator-fury]
chaokunyang opened a new pull request, #1642: URL: https://github.com/apache/incubator-fury/pull/1642 ## What does this PR do? merge main into 0.5.1 ## Related issues ## Does this PR introduce any user-facing change? - [ ] Does this PR introduce any public API change? - [ ] Does this PR introduce any binary protocol compatibility change? ## Benchmark -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
Re: [PR] feat(java): remove soft/weak ref values from thread safe fury [incubator-fury]
MrChang0 commented on PR #1639: URL: https://github.com/apache/incubator-fury/pull/1639#issuecomment-2119806195 fine, if we want remove guava dependency, we can try [caffeine](https://github.com/ben-manes/caffeine), maybe can shaded in fury. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: commits-unsubscr...@fury.apache.org For additional commands, e-mail: commits-h...@fury.apache.org
