You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@answer.apache.org by LinkinStar <li...@apache.org> on 2023/11/02 09:06:10 UTC
About the process of releasing a binary
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
AW: About the process of releasing a binary
Posted by Christofer Dutz <ch...@c-ware.de>.
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 <li...@apache.org>
Datum: Freitag, 3. November 2023 um 07:46
An: dev@answer.apache.org <de...@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 <wi...@gmail.com> 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 <li...@apache.org> 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-unsubscribe@answer.apache.org
> For additional commands, e-mail: dev-help@answer.apache.org
>
>
Re: About the process of releasing a binary
Posted by LinkinStar <li...@apache.org>.
Hi Justin,
In addition to the above mentioned, there is another question I would like
to confirm. Does the binary release need to include the DISCLAIMER file? Of
course, if you find any other missing files please let me know. Thank you
very much!
Best regards,
LinkinStar
On Mon, Nov 6, 2023 at 5:30 PM LinkinStar <li...@apache.org> wrote:
> Hi,
>
> As you say "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." We add the file link to the license in the release LICENSE. We
> draft a release so you can truly understand what would be contained in the
> real release. The link is
> https://github.com/apache/incubator-answer/releases/tag/untagged-5a5c1244f85e5d0976a0.
> You can download the assets and check if we are still missing any files
> when we release the binary. Thanks again for your help.
>
> Best regards,
> LinkinStar
>
>
> On Mon, Nov 6, 2023 at 2:33 PM LinkinStar <li...@apache.org> wrote:
>
>> 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 <ju...@classsoftware.com>
>> 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-unsubscribe@answer.apache.org
>>> For additional commands, e-mail: dev-help@answer.apache.org
>>>
>>>
Re: About the process of releasing a binary
Posted by LinkinStar <li...@apache.org>.
Hi,
As you say "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." We add the file link to the license in the release LICENSE. We
draft a release so you can truly understand what would be contained in the
real release. The link is
https://github.com/apache/incubator-answer/releases/tag/untagged-5a5c1244f85e5d0976a0.
You can download the assets and check if we are still missing any files
when we release the binary. Thanks again for your help.
Best regards,
LinkinStar
On Mon, Nov 6, 2023 at 2:33 PM LinkinStar <li...@apache.org> wrote:
> 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 <ju...@classsoftware.com>
> 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-unsubscribe@answer.apache.org
>> For additional commands, e-mail: dev-help@answer.apache.org
>>
>>
Re: About the process of releasing a binary
Posted by LinkinStar <li...@apache.org>.
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 <ju...@classsoftware.com>
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-unsubscribe@answer.apache.org
> For additional commands, e-mail: dev-help@answer.apache.org
>
>
Re: About the process of releasing a binary
Posted by Justin Mclean <ju...@classsoftware.com>.
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-unsubscribe@answer.apache.org
For additional commands, e-mail: dev-help@answer.apache.org
Re: About the process of releasing a binary
Posted by LinkinStar <li...@apache.org>.
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 <ju...@classsoftware.com>
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 <li...@apache.org> 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 <wi...@gmail.com>
> 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 <li...@apache.org>
> 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-unsubscribe@answer.apache.org
> >> For additional commands, e-mail: dev-help@answer.apache.org
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@answer.apache.org
> For additional commands, e-mail: dev-help@answer.apache.org
>
>
Re: About the process of releasing a binary
Posted by Justin Mclean <ju...@classsoftware.com>.
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 <li...@apache.org> 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 <wi...@gmail.com> 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 <li...@apache.org> 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-unsubscribe@answer.apache.org
>> For additional commands, e-mail: dev-help@answer.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@answer.apache.org
For additional commands, e-mail: dev-help@answer.apache.org
Re: About the process of releasing a binary
Posted by LinkinStar <li...@apache.org>.
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 <wi...@gmail.com> 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 <li...@apache.org> 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-unsubscribe@answer.apache.org
> For additional commands, e-mail: dev-help@answer.apache.org
>
>
Re: About the process of releasing a binary
Posted by Willem Jiang <wi...@gmail.com>.
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 <li...@apache.org> 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-unsubscribe@answer.apache.org
For additional commands, e-mail: dev-help@answer.apache.org
Re: About the process of releasing a binary
Posted by LinkinStar <li...@apache.org>.
OK,
Thanks for the reply. So, If we just use them, we don't need to put
anything on NOTICE about dependencies, right? How about the license? Does
the licence need to include third-party dependencies in the zip containing
the binary in the release? For example, like this
https://github.com/apache/linkis/blob/master/linkis-dist/release-docs/LICENSE
I am not sure and just want to find an example.
Best,
LinkinStar
On Thu, Nov 2, 2023 at 5:14 PM Christofer Dutz <ch...@c-ware.de>
wrote:
> Well,
>
> we don’t release the third-party dependencies, so we theoretically just
> use them, if the licensing is compatible.
>
> If we copy code from third-party projects, we need to keep the license
> headers intact and need to list which files were copied from which project
> and which license they were under in our NOTICE files.
>
> I hope that was correct (Wave in the direction of Justin) ;-)
>
> Chris
>
> Von: LinkinStar <li...@apache.org>
> Datum: Donnerstag, 2. November 2023 um 10:06
> An: dev@answer.apache.org <de...@answer.apache.org>
> Betreff: About the process of releasing a binary
> 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
>
AW: About the process of releasing a binary
Posted by Christofer Dutz <ch...@c-ware.de>.
Well,
we don’t release the third-party dependencies, so we theoretically just use them, if the licensing is compatible.
If we copy code from third-party projects, we need to keep the license headers intact and need to list which files were copied from which project and which license they were under in our NOTICE files.
I hope that was correct (Wave in the direction of Justin) ;-)
Chris
Von: LinkinStar <li...@apache.org>
Datum: Donnerstag, 2. November 2023 um 10:06
An: dev@answer.apache.org <de...@answer.apache.org>
Betreff: About the process of releasing a binary
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