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 <linkins...@apache.org> Datum: Freitag, 3. November 2023 um 07:46 An: dev@answer.apache.org <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 <willem.ji...@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 <linkins...@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-unsubscr...@answer.apache.org > For additional commands, e-mail: dev-h...@answer.apache.org > >
