Re: [VOTE] Release Apache Answer (Incubating) v1.3.6-RC1

HI, +1 (binding) I checked (in the source release): - incubating in artifact name - signatures and hashes are fine - DISCLAIMER exists - LICENSE and NOTICE are good - All ASF files have correct headers - No unexpected binary files I don't have my machine set up to build, but the instructions loo

Re: [RESULT][VOTE] Release Apache Answer, Incubating, v1.2.0-RC1

llowing results: > > 3 (+1 binding) votes > - Justin Mclean > - Shuailing LI > - Feng Dong > > > > I will bring the vote results to gene...@incubator.apache.org > > Thanks, > LinkinStar ---

Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1

Hi, > Thank you for your suggestions. I will update README.md in the v1.2.0 > release version. The compilation process is quite complex, we will put the > process to the official website of the document for detailed explanation. Putting it on the website detached from a release is only sometimes

Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1

Hi, +1 (binding) I checked the source release: - incubating in name - signatures and hashes are fine - DISCLAIMER exists - LICENSE and NOTICE are good - No unexpected binary files - All source files have ASF headers The README.md mentions using docker with the latest; you should not point users

Re: [DISCUSS] Step down or redirect answer.dev

upgraded, then proceed with the redirection. > > Regarding this, do you have any suggestions? Thank you. > > Best, > Nadia > > Justin Mclean 于2023年11月13日周一 03:17写道： > >> redirection would be best >> >> On Mon, 13 Nov 2023, 1:59 pm tison, wrote: >&

Re: [DISCUSS] Step down or redirect answer.dev

redirection would be best On Mon, 13 Nov 2023, 1:59 pm tison, wrote: > Hi, > > Currently, https://answer.dev/ is still online and holds the outdated > information that can diverge the branding of Apache Answer. > > I suggest that we either redirect answer.dev to answer.apache.dev to keep > the c

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 li

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

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 “We’l

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

Re: (incubator-answer) branch main updated: Add NOTICE and DISCLAIMER for release. (#588)

HI, Generally, the company that granted the software to the ASF is mentioned in the NOTICE file, as their copyright statements have been removed. Kind Regards, Justin > On 1 Nov 2023, at 2:24 pm, linkins...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repositor

Re: Checklist for incubator-answer repo

Hi, But I found a few issues assuming all files end up in a release. - missing NOTICE file - missing DISCLAIMER - file without header/or of unknown license [1] - there are a lot of references to https://github.com/answerdev/ and https://answer.dev Kind Regards, Justin 1. ./charts/templates/_hel

Re: Checklist for incubator-answer repo

Hi, In general, only releases need to comply, and the LICENSE and NOTICE files need to match what is in the release, not the repo. Kind Regards, Justin > On 31 Oct 2023, at 8:12 pm, Feng Dong wrote: > > Hello everyone, > > I created a checklist to ensure that the code repo complies w