AW: About the process of releasing a binary

[Christofer Dutz]

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 source-releases, you only need to add to the NOTICE, what’s in 
there … if there’s for example a maven pom.xml referencing a third party 
library – that’s not IN the source-release, so no need to add it.
If you build maven binaries and deploy them to maven central, usually you only 
deploy the code of the module itself and the other stuff is pulled in via 
dependency. So also no need to mention it.

However, if you build something like a “distribution” or you bundle other 
artifacts in your artifacts as some “fat-jars” then the other stuff is in there 
and it needs to be added to the NOTICE of the binary.

I hope that explains things a bit.

Chris



Von: LinkinStar 
Datum: Freitag, 3. November 2023 um 07:46
An: dev@answer.apache.org 
Betreff: Re: About the process of releasing a binary
Get it.

Then we will collect all the dependency's licences for the binary release.

Best,
LinkinStar

On Fri, Nov 3, 2023 at 2:20 PM Willem Jiang  wrote:

> Here are some instructions[1] about composing the License and Notice file.
> If we provide the binary release, we must include the License file of
> third-party dependencies.
>
> [1] https://infra.apache.org/licensing-howto.html
>
>
> Willem Jiang
>
> On Thu, Nov 2, 2023 at 5:07 PM LinkinStar  wrote:
> >
> > Hi,
> >
> > We are learning about the process of releasing a binary and have
> > encountered a few problems. 1. If our third-party dependencies don't have
> > the NOTICE, do we just need our own NOTICE when we release a binary? 2.
> I'd
> > like to ask if there are any Golang projects that have released binaries
> in
> > the past that I can learn from.
> >
> > Thanks. Regards
>
> -
> 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

[Justin Mclean]

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 Regards,
Justin


> On 3 Nov 2023, at 5:46 pm, LinkinStar  wrote:
> 
> Get it.
> 
> Then we will collect all the dependency's licences for the binary release.
> 
> Best,
> LinkinStar
> 
> On Fri, Nov 3, 2023 at 2:20 PM Willem Jiang  wrote:
> 
>> Here are some instructions[1] about composing the License and Notice file.
>> If we provide the binary release, we must include the License file of
>> third-party dependencies.
>> 
>> [1] https://infra.apache.org/licensing-howto.html
>> 
>> 
>> Willem Jiang
>> 
>> On Thu, Nov 2, 2023 at 5:07 PM LinkinStar  wrote:
>>> 
>>> Hi,
>>> 
>>> We are learning about the process of releasing a binary and have
>>> encountered a few problems. 1. If our third-party dependencies don't have
>>> the NOTICE, do we just need our own NOTICE when we release a binary? 2.
>> I'd
>>> like to ask if there are any Golang projects that have released binaries
>> in
>>> the past that I can learn from.
>>> 
>>> Thanks. Regards
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
>> For additional commands, e-mail: dev-h...@answer.apache.org
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
For additional commands, e-mail: dev-h...@answer.apache.org

Contribution PR messages

[Justin Mclean]

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 “We’ll merge 
the changes at the next release” or something else? 

Kind Regards,
Justin
-
To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
For additional commands, e-mail: dev-h...@answer.apache.org

Re: Contribution PR messages

[Enxin Xie]

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 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 “We’ll 
> merge the changes at the next release” or something else? 
> 
> Kind Regards,
> Justin
> -
> To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
> For additional commands, e-mail: dev-h...@answer.apache.org
> 
> 

-
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

[LinkinStar]

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? Thank you very much.

Best regards,
LinkinStar

On Sun, Nov 5, 2023 at 11:45 PM Justin Mclean 
wrote:

> 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 Regards,
> Justin
>
>
> > On 3 Nov 2023, at 5:46 pm, LinkinStar  wrote:
> >
> > Get it.
> >
> > Then we will collect all the dependency's licences for the binary
> release.
> >
> > Best,
> > LinkinStar
> >
> > On Fri, Nov 3, 2023 at 2:20 PM Willem Jiang 
> wrote:
> >
> >> Here are some instructions[1] about composing the License and Notice
> file.
> >> If we provide the binary release, we must include the License file of
> >> third-party dependencies.
> >>
> >> [1] https://infra.apache.org/licensing-howto.html
> >>
> >>
> >> Willem Jiang
> >>
> >> On Thu, Nov 2, 2023 at 5:07 PM LinkinStar 
> wrote:
> >>>
> >>> Hi,
> >>>
> >>> We are learning about the process of releasing a binary and have
> >>> encountered a few problems. 1. If our third-party dependencies don't
> have
> >>> the NOTICE, do we just need our own NOTICE when we release a binary? 2.
> >> I'd
> >>> like to ask if there are any Golang projects that have released
> binaries
> >> in
> >>> the past that I can learn from.
> >>>
> >>> Thanks. Regards
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
> >> For additional commands, e-mail: dev-h...@answer.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
> For additional commands, e-mail: dev-h...@answer.apache.org
>
>

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

[Justin Mclean]

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
 


Is that getting something from a private repository?

Kind Regards,
Justin

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

[Justin Mclean]

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 license in the release. With the second option, some projects make 
a licenses directory and put all of the licenses there.

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

[Justin Mclean]

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
-
To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
For additional commands, e-mail: dev-h...@answer.apache.org

Re: Contribution PR messages

[Justin Mclean]

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: [I] Unable to install UI dependencies [incubator-answer]

[Shuailing LI]

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!

Best,
shuai



Justin Mclean  于2023年11月6日周一 12:35写道：

> 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
> <
> https://repository-private-36320838.d.codeartifact.us-west-2.amazonaws.com/npm/react-web-shared-components/codemirror/-/codemirror-5.65.0.tgz
> :>
>
> Is that getting something from a private repository?
>
> Kind Regards,
> Justin

Re: About the process of releasing a binary

[LinkinStar]

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:

> 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
> -
> To unsubscribe, e-mail: dev-unsubscr...@answer.apache.org
> For additional commands, e-mail: dev-h...@answer.apache.org
>
>