ammachado commented on PR #24915:
URL: https://github.com/apache/camel/pull/24915#issuecomment-5023902442

   _Claude Code on behalf of Adriano Machado (ammachado)_
   
   Status update on the pieces of CAMEL-23703:
   
   | Component | Status |
   |---|---|
   | Java runtime discovery for camel.sh/camel.bat | Merged 
(apache/camel#24664) |
   | Native camel.exe bootstrap (Windows) | Merged (apache/camel#24665) |
   | Cross-compile camel.exe for x64/arm64 | Merged (apache/camel#24754) |
   | Website installer scripts (install.sh/install.ps1) + release manifests | 
Merged (apache/camel#24682) |
   | JReleaser packaging (Homebrew, SDKMAN, WinGet, Scoop, Chocolatey) | Open, 
in review (this PR, #24915) |
   | Package-native validation CI (installs/uninstalls each generated package 
and smoke-tests it) | Prepared; PR will follow once this one merges |
   
   Not yet started:
   
   - **Actual publishing to the package managers.** Everything above only 
prepares/packages the artifacts locally; nothing pushes a release to Homebrew, 
SDKMAN, WinGet, Scoop, or Chocolatey yet. This needs a PMC decision on publish 
destinations first, e.g. whether Homebrew formulae go to this project's own tap 
or to homebrew-core, since that decision shapes how publishing gets wired up. 
It also blocks producing both the unversioned and versioned Homebrew formula 
from a single release.
   - **Making install.sh/install.ps1 reachable at camel.apache.org.** The 
scripts are done and tested, but nothing serves them yet, so `curl -fsSL 
https://camel.apache.org/install.sh` doesn't resolve. That requires a change in 
the camel-website repo; the tracking issue there (apache/camel-website#1487) is 
still open with no PR against it.
   
   Let me know if there's a preference on the Homebrew tap question so 
publishing can move forward.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to