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 <[email protected]> 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 <[email protected]> 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 <[email protected]> >> 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: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>>
