Something like that would work. This change does not need to block this RC vote but I think it would be better if future RC archives had a structure like this.
The highest priority now though is to cancel the incubator vote and to concentrate on starting a discussion thread on d...@answer.apache.org. Generally, releases start with a discussion thread and then a vote and later, result. Then you can move to starting a vote thread on general@incubator.apache.org. On Wed, 15 Nov 2023 at 11:28, LinkinStar <linkins...@apache.org> wrote: > > Hi PJ, > > I just want to make sure. According to your description, the final bin tar.gz > should contain something like the following format right? > > apache-answer-1.2.0/ (everything are in this folder) > ├── DISCLAIMER (text) > ├── LICENSE (text) > ├── NOTICE (text) > ├── answer (binary) > └── licenses (directory) > > Thanks, > LinkinStar > > > On Wed, Nov 15, 2023 at 6:12 PM PJ Fanning <fannin...@gmail.com> wrote: >> >> Hi LinkinStar, >> >> Could you also review what I sent in >> https://lists.apache.org/thread/rklvd9vsm7q64l21n045k8ffh4lc622s ? I >> didn't include you in the send list for that mail. >> >> And a further request, could you modify the directory format of the >> bin tar.gz files. I would suggest that there should be a top level >> directory. At the moment, the files are in this format. >> >> DISCLAIMER >> LICENSE >> NOTICE >> answer >> licenses >> >> The top 3 are text files and answer and licenses are directories. It >> might be tidier to put everything in the answer folder. Would it be >> feasible to add the `apache` to the name? And the version number (eg >> 1.2.0). >> >> >> On Wed, 15 Nov 2023 at 10:22, LinkinStar <linkins...@apache.org> wrote: >> > >> > Hi PJ, >> > >> > Thank you very much for your suggestion. I'll rename the directory to >> > 1.2.0-incubating-RC1 and use v1.2.0-RC1 tag. >> > >> > Thanks, >> > LinkinStar >> > >> > On Wed, Nov 15, 2023 at 5:12 PM PJ Fanning <fannin...@apache.org> wrote: >> > >> > > Another issue with the email is it should include the git commit id. >> > > Tags are good too - but tags can be moved. >> > > This is my preference but I think it would be better if you have a >> > > v1.2.0-RC1 tag and then add a v1.2.0 tag only when the 2 votes pass. >> > > >> > > On Wed, 15 Nov 2023 at 10:07, PJ Fanning <fannin...@apache.org> wrote: >> > > > >> > > > Hi LinkinStar, >> > > > >> > > > You need to include details of the Apache Answer vote. In a quick >> > > > search, I can find no evidence that there has been a vote on your dev >> > > > list. >> > > > >> > > > https://lists.apache.org/list.html?d...@answer.apache.org >> > > > >> > > > Incubator podlings need to first do a vote on their dev list and that >> > > > vote requires at least 3 +1s from Answer PPMC members. When that >> > > > passes, you then must run a 2nd vote on the Incubator general list. >> > > > The incubator vote needs at least 3 +1s from Incubator PMC members >> > > > (binding votes). >> > > > >> > > > Also, it's standard to include `-RC1` in the dist.apache.org directory >> > > > name. This means that if your RC1 fails, you can do an RC2. The >> > > > filenames don't include the RC1. >> > > > >> > > > I would suggest renaming the directory to >> > > > >> > > > >> > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating-RC1/ >> > > > >> > > > When the votes pass you can move this to >> > > > >> > > > >> > > https://dist.apache.org/repos/dist/release/incubator/answer/1.2.0-incubating/ >> > > > >> > > > Regards, >> > > > PJ >> > > > >> > > > On Wed, 15 Nov 2023 at 09:51, LinkinStar <linkins...@apache.org> wrote: >> > > > > >> > > > > Hello, >> > > > > >> > > > > This is a call for vote to release Apache Answer(Incubating) >> > > version >> > > > > v1.2.0. >> > > > > >> > > > > The release candidates: >> > > > > >> > > > > >> > > https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating/ >> > > > > >> > > > > Release notes: >> > > > > >> > > > > https://github.com/apache/incubator-answer/releases/tag/v1.2.0 >> > > > > >> > > > > Git tag for the release: >> > > > > >> > > > > https://github.com/apache/incubator-answer/releases/tag/v1.2.0 >> > > > > >> > > > > Keys to verify the Release Candidate: >> > > > > https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS >> > > > > >> > > > > The vote will be open for at least 72 hours or until the >> > > > > necessary >> > > > > number of votes are reached. >> > > > > >> > > > > Please vote accordingly: >> > > > > >> > > > > [ ] +1 approve >> > > > > [ ] +0 no opinion >> > > > > [ ] -1 disapprove with the reason >> > > > > >> > > > > Checklist for reference: >> > > > > >> > > > > [ ] Download links are valid. >> > > > > [ ] Checksums and PGP signatures are valid. >> > > > > [ ] Source code distributions have correct names matching the >> > > current >> > > > > release. >> > > > > [ ] LICENSE and NOTICE files are correct for each Answer repo. >> > > > > [ ] All files have license headers if necessary. >> > > > > [ ] No unlicensed compiled archives bundled in source archive. >> > > > > >> > > > > Thanks, >> > > > > LinkinStar >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> > > For additional commands, e-mail: general-h...@incubator.apache.org >> > > >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
