Open tiagobento opened 7 months ago
For Apache KIE 10.0, we'll still rely on manually editing code on https://github.com/apache/incubator-kie-sandbox-quarkus-accelerator/tree/0.0.0, but for 10.1 and beyond, we'll produce the source of the Accelerator from kie-tools
, and we'll treat it as a release artifact. https://github.com/apache/incubator-kie-sandbox-quarkus-accelerator will become a hosting repo only (no development), just like https://github.com/apache/incubator-kie-kogito-online hosts the GitHub Pages deployment of KIE Sandbox.
Our daily-dev builds should continue updating the 0.0.0 branch, although I think it would be better to switch for main
instead, to follow the "streams" we have setup for container images too...
Added a TODO list in the description of this issues.
Instead of maintaining the code directly on https://github.com/apache/incubator-kie-sandbox-quarkus-accelerator, we should just move the code to a package on
kie-tools
and push it to https://github.com/apache/incubator-kie-sandbox-quarkus-accelerator as part of the release process. This will make sure this repo is always in sync with the rest ofkie-tools
.Locally, when developing KIE Sandbox, we should spawn a Git server so that KIE Sandbox can clone the Accelerator code from it.
TODO:
kie-tools
as a new package (packages/kie-sandbox-accelerator-quarkus
)template
,0.0.0
, and10.0.999
) from https://github.com/apache/incubator-kie-sandbox-quarkus-acceleratormain
'sdaily-dev
(https://ci-builds.apache.org/job/KIE/job/kie-tools/job/main/job/kie-tools-daily-dev-publish/) is publishing to themain
branch correctly.10.0.x
'sweekly
(https://ci-builds.apache.org/job/KIE/job/kie-tools/job/10.0.x/job/kie-tools-weekly-publish/) is publishing to the10.0.x
branch correctly.packages/kie-sandbox-accelerator-quarkus