Thanks for the additional information, Tison! Really appreciate it.
Certainly right after the release this will be a top priority for me.
The Apache KIE project publishes a lot of artifacts to a lot of
different places, so this is all a little bit overwhelming to do for a
first release. I'm glad
Hi Tiago,
> How? Every package we ever published to NPM under KIE is owned by
> https://www.npmjs.com/~kie-tools-bot now (some of them were
> removed/renamed). We can give control to the ~theasf user, no problem.
You can open an INFRA JIRA ticket like [1].
[1]
Thanks all for the replies.
I'll try to postpone renaming the packages we have today, so we'll
start the release vote without this renaming. All packages will
include the DISCLAIMER in their README files. E.g.,
https://github.com/apache/incubator-kie-tools/blob/main/packages/dmn-editor/README.md
Here’s my 2 cents.
Incubation is a journey, and if there are parts that are yet to be compliant
that should be fine. In the end all will be squared away.
For the IPMC - should we have something like DISCLAIMER-WIP for binary
convenience packaging?
Best,
Dave
> On May 15, 2024, at 1:13 PM,
Tison,
Thanks for the reply!
On Wed, May 15, 2024 at 1:43 PM tison wrote:
>
> We have an official account on NPM [1] and the associated org [2] (cc @Mark
> Thomas IIRC who manages this account).
>
> [1] https://www.npmjs.com/~theasf
> [2] https://www.npmjs.com/org/apache
>
> Both of these
We have an official account on NPM [1] and the associated org [2] (cc @Mark
Thomas IIRC who manages this account).
[1] https://www.npmjs.com/~theasf
[2] https://www.npmjs.com/org/apache
Both of these associations can improve the verification and brand for your
release, while you may use the
Shawn,
Does that mean you didn't publish anything to NPM as part of your
releases while in the incubator?
On Wed, May 15, 2024 at 12:31 PM Shawn Yang wrote:
>
> Hi Tiago,
>
> From the current incubator release policy, you need to rename all npm
> packages to apache-xxx before releasing. The
Hi Tiago,
>From the current incubator release policy, you need to rename all npm
packages to apache-xxx before releasing. The packages released before
should be on to left intact.
I came across same issue when we release apache fury. In your case, most
packages starts with kie. Fury has similar
Podlings are allowed some leeway. Ideally, you should aim to eventually
rename your binary artifacts to include Apache KIE branding. I think it
should be ok to make an initial release with the existing naming,
especially if you comply with the other requirements in the NPM
distribution guidelines
Hi general@incubator,
The distribution guidelines [1] say packages published to NPM should
be named `apache-`, however, at KIE, we have a somewhat big
set of packages that are published under these scopes:
- @kie-tools/*
- @kie-tools-core/*
- @kie-tools-scripts/*
There are also some VS Code
10 matches
Mail list logo
