You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@orc.apache.org by do...@apache.org on 2024/01/13 02:07:32 UTC
(orc) branch branch-2.0 updated: ORC-1100: Add vcpkg release document
This is an automated email from the ASF dual-hosted git repository.
dongjoon pushed a commit to branch branch-2.0
in repository https://gitbox.apache.org/repos/asf/orc.git
The following commit(s) were added to refs/heads/branch-2.0 by this push:
new 395b8a958 ORC-1100: Add vcpkg release document
395b8a958 is described below
commit 395b8a958454ef68d183eb6d4578626a0c818944
Author: deshanxiao <de...@microsoft.com>
AuthorDate: Fri Jan 12 18:07:17 2024 -0800
ORC-1100: Add vcpkg release document
### What changes were proposed in this pull request?
This PR is aimed to add vcpkg document to note how to update vcpkg package when we release a new version.
### Why are the changes needed?
To help release manager to release our latest package in vcpkg.
### How was this patch tested?
N/A
### Was this patch authored or co-authored using generative AI tooling?
No
Closes #1746 from deshanxiao/deshan/update-doc.
Authored-by: deshanxiao <de...@microsoft.com>
Signed-off-by: Dongjoon Hyun <do...@apache.org>
(cherry picked from commit c87707c53bd2a461c292272d014d2e13076bdf99)
Signed-off-by: Dongjoon Hyun <do...@apache.org>
---
site/develop/make-release.md | 48 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
diff --git a/site/develop/make-release.md b/site/develop/make-release.md
index 38edd2541..25262015a 100644
--- a/site/develop/make-release.md
+++ b/site/develop/make-release.md
@@ -188,3 +188,51 @@ Update ORC's jira to reflect the released version.
* Mark the version as released and set the date [here](https://issues.apache.org/jira/projects/ORC?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page).
It usually take up to 24 hours for the apache dist mirrors and maven central to update with the new release.
+
+## To release ORC in vcpkg.
+We could release the latest ORC version in [vcpkg](https://vcpkg.io/en/packages).
+
+1.Download the source code of vcpkg:
+~~~
+% git clone git@github.com:microsoft/vcpkg.git
+~~~
+
+2.Compile vcpkg
+
+Configure your vcpkg based on operating system versions. See [Getting Started](https://github.com/microsoft/vcpkg?tab=readme-ov-file#getting-started)
+
+3.Update ORC version
+
+Update the **version** field of [vcpkg.json](https://github.com/microsoft/vcpkg/blob/master/ports/orc/vcpkg.json). Run the following command to rebuild ORC:
+```
+% ./vcpkg build orc
+```
+
+You will receive an error, which contains a SHA512 value, updating it to the [portfile.cmake](https://github.com/microsoft/vcpkg/blob/master/ports/orc/portfile.cmake) file.
+
+> Expected hash: 141afbd6d83b8c8032df071838e7da61eedb3d22289642f76669b6efd167d7550b200bd3542f012d0b63c9ae2572d83fcb1b7f76537b6fa6f980aebf37e2cde2
+
+> Actual hash (you should update): 7b9d6f9613f48b41843618465c0c71ed70e5695b4fc4b3db15d0bbfe4c5126e0c6c8f1114d6c450a56b4ddf0357d89bd40cb03c0964275c59761cc0f8fec1291
+
+4.Commit current changes
+```
+% git commit -m ""
+```
+
+Run ./vcpkg x-add-version --all to auto generate version item in version database.
+```
+% ./vcpkg x-add-version --all
+```
+
+Test changes with the following command:
+```
+% ./vcpkg build orc
+```
+
+If anything is ok, re-commit changes and send a PR to [vcpkg repo](https://github.com/microsoft/vcpkg).
+
+This is an [example](https://github.com/microsoft/vcpkg/pull/36098/files) of updating to ORC 1.9.2
+
+> Note: You will not immediately find the merged PR version on the official website of vcpkg. check [vcpkg release](https://github.com/microsoft/vcpkg/releases) to know the latest release progress.
+
+