Re: About the process of releasing a binary

Hi, OK, as you say in the other email, we will use the file link instead of the http link in the LICENSE . After that, we will build a draft release so you can see what would be contained in the real release. Best regards, LinkinStar On Mon, Nov 6, 2023 at 12:50 PM Justin Mclean wrote: >

Re: [I] Unable to install UI dependencies [incubator-answer]

Oh, All dependencies used in our project come from public repositories.This link comes from an issu (#602). I tested it according to his version control, and this problem did not occur, so this is most likely related to its local network proxy. I will continue to pay attention to this issue!

Re: Contribution PR messages

Hi, Thanks for clearing that up. Kind Regards, Justin - To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org For additional commands, e-mail: dev-h...@answer.apache.org

Re: About the process of releasing a binary

HI, It would not, as you need to include the full text of the licenses as must require this - see my other email. I’d also need a release to compare it with. Looking at the various readmes etc,. it’s unclear to me how I build this or what a release would contain. Kind Regards, Justin

Re: (incubator-answer) branch podling updated: feat: update license list

Hi, This doesn't look correct to me: A) Only things included in the release need to be mentioned, not all dependencies. B) Most licenses dictate that you need to include the full text of the license. For B), this can be done in LICENSE, or you can include a file link (not a http link) to the

Re: [I] Unable to install UI dependencies [incubator-answer]

Hi, I don’t know the build process, and I may have no idea what I’m talking about, but that URL seems a bit odd to me: GET https://repository-private-36320838.d.codeartifact.us-west-2.amazonaws.com/npm/react-web-shared-components/codemirror/-/codemirror-5.65.0.tgz

Re: About the process of releasing a binary

Hi, As you say, we list all licenses that are included in the release. The link is https://github.com/apache/incubator-answer/blob/f1d20307494690f8d919f3f40b98fdb19da80925/docs/release/LICENSE#L211 But we are not sure that such a format would meet the requirements. Could you help us review it?

Re: Contribution PR messages

Hi, I'm very sorry, my expression was ambiguous. I means, after we've tested it and it's OK, we will merge this PR. But the actual changes will be shown in the next release. Best, LinkinStar On 2023/11/06 03:14:54 Justin Mclean wrote: > Hi, > > I’ve noticed a couple of messages on PRs that

Contribution PR messages

Hi, I’ve noticed a couple of messages on PRs that state, "Thanks for the contribution, this PR will be merged in the next version.”. That's a nice welcoming message so tha'st great, but does it mean, “We’ll merge this right away, and your changes will show up in the next release”, or that

Re: About the process of releasing a binary

HI, And you don't "collect all the dependency's licences for the binary release.” you only need to list licenses of anything that is included in the release. Dependencies that ae not included don’t need to be mentioned. This is described in more detail at the URL Chris provided. Kind

AW: About the process of releasing a binary

Well … technically we don’t „release“ binaries. Apache generally only releases sources and the binaries are considered “convenience binaries”. There is some momentum with changing this, but currently I think we’re still at the point where we don’t call them “releases”. So for your