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

2023-11-15 Thread PJ Fanning
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  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



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

2023-11-15 Thread PJ Fanning
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  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  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



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

2023-11-15 Thread LinkinStar
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  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  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  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
>
>


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

2023-11-15 Thread Buffer Support
-- Please reply above this line --


Please kindly unsubscribe he...@buffer.com [1] 


Links:
--
[1] mailto:he...@buffer.com


How would you rate my reply?
Great [1]    Okay [2]    Not Good [3]



Links:
--
[1]
https://secure.helpscout.net/satisfaction/658516046/record/7256892908/1/
[2]
https://secure.helpscout.net/satisfaction/658516046/record/7256892908/2/
[3]
https://secure.helpscout.net/satisfaction/658516046/record/7256892908/3/





> On Wed, Nov 15, 2023 at 4:21:49 EST,  
 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 4:12:18 EST,   
>> 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, Nov 15, 2023 at 4:08:16 EST,   
>>> 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 [1]
>>>
>>> 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/
>>> [2]
>>>
>>> When the votes pass you can move this to
>>>
>>> https://dist.apache.org/repos/dist/release/incubator/answer/1.2.0-incubating/
>>> [3]
>>>
>>> Regards,
>>> PJ
>>>
>>> Links:
>>> --
>>> [1] https://lists.apache.org/list.html?d...@answer.apache.org
>>> [2]
>>> https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating-RC1/
>>> [3]
>>> https://dist.apache.org/repos/dist/release/incubator/answer/1.2.0-incubating/
>>>
>>>
>>>
 On Wed, Nov 15, 2023 at 3:51:24 EST,   
 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/
 [1]

 Release notes:
 https://github.com/apache/incubator-answer/releases/tag/v1.2.0 [2]

 Git tag for the release:
 https://github.com/apache/incubator-answer/releases/tag/v1.2.0 [3]

 Keys to verify the Release Candidate:
 https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS [4]

 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

 Links:
 --
 [1]
 https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating/
 [2] https://github.com/apache/incubator-answer/releases/tag/v1.2.0
 [3] https://github.com/apache/incubator-answer/releases/tag/v1.2.0
 [4] https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS




>>>
>>
> 



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

2023-11-15 Thread PJ Fanning
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  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  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  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  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



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

2023-11-15 Thread PJ Fanning
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  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  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  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  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  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  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

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

2023-11-15 Thread LinkinStar
Thanks for your advice.

On Wed, Nov 15, 2023 at 6:42 PM PJ Fanning  wrote:

> 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  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  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  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 
> 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 
> 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 
> 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.
> >> > > > > [ ] C

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

2023-11-17 Thread PJ Fanning
-1 (binding)

The Answer vote was not left open for at least 72 hours. That vote
must be reopened and you must wait at least 72 hours from the initial
calling of the vote before announcing a result.

On Fri, 17 Nov 2023 at 04:06, LinkinStar  wrote:
>
> Hello,
>
> This is a call for vote to release Apache Answer(Incubating) version
> v1.2.0-RC1.
>
> The vote thread:
> https://lists.apache.org/thread/jjcq356m26gvstbo2jbojt42q7t91xyp
>
> Vote Result:
> https://lists.apache.org/thread/z8dgv2wwkwvq53gc7hvv36bcbd5xry49
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating-RC1/
>
> Release notes:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.0-RC1
>
> Git tag for the release:
> https://github.com/apache/incubator-answer/releases/tag/v1.2.0-RC1
>
> Git commit id for the release:
>
> https://github.com/apache/incubator-answer/commit/8a3b19fd32fabae4eed98a1f240a01f27bebdf5f
>
> 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.
>
> To compile from the source, please refer to:
>
> https://github.com/apache/incubator-answer#building-from-source
>
> Thanks,
> LinkinStar

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



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

2023-11-19 Thread Justin Mclean
Hi,

+1 (binding) - carrying over my vote from the dev list.

Kind Regards,
Justin

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org



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

2023-11-28 Thread Feng Dong
+1 (non-binding)

On Mon, Nov 20, 2023 at 5:31 PM Christofer Dutz 
wrote:

> +1 (binding)
>
> Chris
>
> [OK] Download all staged artifacts under the url specified in the release
> vote email.
> [OK] Verify the signature is correct.
> [OK] Check if the signature references an Apache email address.
> [OK] Verify the SHA512 hashes.
> [OK] Unzip the archive.
> [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files in
> the extracted source bundle.
> [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in
> the extracted source bundle.
>
>   *   No WIP disclaimer, doing full checks.
> [OK] Run RAT externally to ensure there are no surprises.
> [OK] Search for Copyright references, and if they are in headers, make
> sure these files containing them are mentioned in the LICENSE file.
> [SKIPPED] Build the project according to the information in the README.md
> file.
>   - No guides on how to build the project
>
>
> Von: Justin Mclean 
> Datum: Sonntag, 19. November 2023 um 22:46
> An: incubator general apache 
> Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
> Hi,
>
> +1 (binding) - carrying over my vote from the dev list.
>
> Kind Regards,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>


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

2023-11-28 Thread tison
+1 (binding)

I checked -
[x] Download links valid
[x] apache & incubating in name
[x] LICENSE and NOTICE present
[x] Checksum and GPG sign matches
[x] DISCLAIMER present
[x] Can compile from source with `make ui; make build`

note: for building, you may need to install mockgen first: go install
go.uber.org/mock/mockgen@latest;
also, there is a warning fatal: not a git repository (or any of the
parent directories): .git that may be improved.

nit: You can use https://downloads.apache.org/incubator/answer/KEY
instead of https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS
the next time (it should be there once you release the first version
to https://dist.apache.org/repos/dist/release/incubator/answer) - See
https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04 for
reference.

Best,
tison.

Christofer Dutz  于2023年11月28日周二 20:49写道:
>
> Would be cool, if one more IPMC member would be willing to give this release 
> a vote…. Admittedly it’s in really good shape and therefore just a minimal 
> bit of work.
>
> Chris
>
>
> Von: Feng Dong 
> Datum: Dienstag, 28. November 2023 um 10:41
> An: general@incubator.apache.org 
> Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
> +1 (non-binding)
>
> On Mon, Nov 20, 2023 at 5:31 PM Christofer Dutz 
> wrote:
>
> > +1 (binding)
> >
> > Chris
> >
> > [OK] Download all staged artifacts under the url specified in the release
> > vote email.
> > [OK] Verify the signature is correct.
> > [OK] Check if the signature references an Apache email address.
> > [OK] Verify the SHA512 hashes.
> > [OK] Unzip the archive.
> > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files in
> > the extracted source bundle.
> > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in
> > the extracted source bundle.
> >
> >   *   No WIP disclaimer, doing full checks.
> > [OK] Run RAT externally to ensure there are no surprises.
> > [OK] Search for Copyright references, and if they are in headers, make
> > sure these files containing them are mentioned in the LICENSE file.
> > [SKIPPED] Build the project according to the information in the README.md
> > file.
> >   - No guides on how to build the project
> >
> >
> > Von: Justin Mclean 
> > Datum: Sonntag, 19. November 2023 um 22:46
> > An: incubator general apache 
> > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
> > Hi,
> >
> > +1 (binding) - carrying over my vote from the dev list.
> >
> > Kind Regards,
> > Justin
> >
> > -
> > 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



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

2023-11-28 Thread tison
The unzipped folder is named as "incubator-answer-1.2.0-RC1", this can
be improved also - keep the same as
"apache-answer-1.2.0-incubating-src".

Best,
tison.

tison  于2023年11月28日周二 21:00写道:
>
> +1 (binding)
>
> I checked -
> [x] Download links valid
> [x] apache & incubating in name
> [x] LICENSE and NOTICE present
> [x] Checksum and GPG sign matches
> [x] DISCLAIMER present
> [x] Can compile from source with `make ui; make build`
>
> note: for building, you may need to install mockgen first: go install
> go.uber.org/mock/mockgen@latest;
> also, there is a warning fatal: not a git repository (or any of the
> parent directories): .git that may be improved.
>
> nit: You can use https://downloads.apache.org/incubator/answer/KEY
> instead of https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS
> the next time (it should be there once you release the first version
> to https://dist.apache.org/repos/dist/release/incubator/answer) - See
> https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04 for
> reference.
>
> Best,
> tison.
>
> Christofer Dutz  于2023年11月28日周二 20:49写道:
> >
> > Would be cool, if one more IPMC member would be willing to give this 
> > release a vote…. Admittedly it’s in really good shape and therefore just a 
> > minimal bit of work.
> >
> > Chris
> >
> >
> > Von: Feng Dong 
> > Datum: Dienstag, 28. November 2023 um 10:41
> > An: general@incubator.apache.org 
> > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
> > +1 (non-binding)
> >
> > On Mon, Nov 20, 2023 at 5:31 PM Christofer Dutz 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Chris
> > >
> > > [OK] Download all staged artifacts under the url specified in the release
> > > vote email.
> > > [OK] Verify the signature is correct.
> > > [OK] Check if the signature references an Apache email address.
> > > [OK] Verify the SHA512 hashes.
> > > [OK] Unzip the archive.
> > > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files in
> > > the extracted source bundle.
> > > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in
> > > the extracted source bundle.
> > >
> > >   *   No WIP disclaimer, doing full checks.
> > > [OK] Run RAT externally to ensure there are no surprises.
> > > [OK] Search for Copyright references, and if they are in headers, make
> > > sure these files containing them are mentioned in the LICENSE file.
> > > [SKIPPED] Build the project according to the information in the README.md
> > > file.
> > >   - No guides on how to build the project
> > >
> > >
> > > Von: Justin Mclean 
> > > Datum: Sonntag, 19. November 2023 um 22:46
> > > An: incubator general apache 
> > > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
> > > Hi,
> > >
> > > +1 (binding) - carrying over my vote from the dev list.
> > >
> > > Kind Regards,
> > > Justin
> > >
> > > -
> > > 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



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

2023-11-28 Thread tison
Wait a minute, this may be a -1 reason:

We just publish the RC artifacts as is, so the formal release that
users will get is a tarball that is unzipped to
"incubator-answer-1.2.0-RC1".

The folder/file name is once a concern[1] although it's a missing
"incubating" in the tarball name that is referred to there.

Best,
tison.

[1] https://lists.apache.org/thread/08sjn6c96tr2kyztwr5k31gl0km6wghg

tison  于2023年11月28日周二 21:01写道:
>
> The unzipped folder is named as "incubator-answer-1.2.0-RC1", this can
> be improved also - keep the same as
> "apache-answer-1.2.0-incubating-src".
>
> Best,
> tison.
>
> tison  于2023年11月28日周二 21:00写道:
> >
> > +1 (binding)
> >
> > I checked -
> > [x] Download links valid
> > [x] apache & incubating in name
> > [x] LICENSE and NOTICE present
> > [x] Checksum and GPG sign matches
> > [x] DISCLAIMER present
> > [x] Can compile from source with `make ui; make build`
> >
> > note: for building, you may need to install mockgen first: go install
> > go.uber.org/mock/mockgen@latest;
> > also, there is a warning fatal: not a git repository (or any of the
> > parent directories): .git that may be improved.
> >
> > nit: You can use https://downloads.apache.org/incubator/answer/KEY
> > instead of https://dist.apache.org/repos/dist/dev/incubator/answer/KEYS
> > the next time (it should be there once you release the first version
> > to https://dist.apache.org/repos/dist/release/incubator/answer) - See
> > https://lists.apache.org/thread/g9040zdg0wk5sdl3ovxgnr86wgtr8m04 for
> > reference.
> >
> > Best,
> > tison.
> >
> > Christofer Dutz  于2023年11月28日周二 20:49写道:
> > >
> > > Would be cool, if one more IPMC member would be willing to give this 
> > > release a vote…. Admittedly it’s in really good shape and therefore just 
> > > a minimal bit of work.
> > >
> > > Chris
> > >
> > >
> > > Von: Feng Dong 
> > > Datum: Dienstag, 28. November 2023 um 10:41
> > > An: general@incubator.apache.org 
> > > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
> > > +1 (non-binding)
> > >
> > > On Mon, Nov 20, 2023 at 5:31 PM Christofer Dutz 
> > > 
> > > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > Chris
> > > >
> > > > [OK] Download all staged artifacts under the url specified in the 
> > > > release
> > > > vote email.
> > > > [OK] Verify the signature is correct.
> > > > [OK] Check if the signature references an Apache email address.
> > > > [OK] Verify the SHA512 hashes.
> > > > [OK] Unzip the archive.
> > > > [OK] Verify the existence of LICENSE, NOTICE, DISCLAIMER, README files 
> > > > in
> > > > the extracted source bundle.
> > > > [OK] Verify the content of LICENSE, NOTICE, DISCLAIMER, README files in
> > > > the extracted source bundle.
> > > >
> > > >   *   No WIP disclaimer, doing full checks.
> > > > [OK] Run RAT externally to ensure there are no surprises.
> > > > [OK] Search for Copyright references, and if they are in headers, make
> > > > sure these files containing them are mentioned in the LICENSE file.
> > > > [SKIPPED] Build the project according to the information in the 
> > > > README.md
> > > > file.
> > > >   - No guides on how to build the project
> > > >
> > > >
> > > > Von: Justin Mclean 
> > > > Datum: Sonntag, 19. November 2023 um 22:46
> > > > An: incubator general apache 
> > > > Betreff: Re: [VOTE] Release Apache Answer(Incubating) v1.2.0-RC1
> > > > Hi,
> > > >
> > > > +1 (binding) - carrying over my vote from the dev list.
> > > >
> > > > Kind Regards,
> > > > Justin
> > > >
> > > > -
> > > > 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



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

2023-11-28 Thread Justin Mclean
Hi,

The release artefacts include incubating in their names [1] as Incubator policy 
requires [2].

Kind Regards,
Justin

1. https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating-RC1/
2. https://incubator.apache.org/policy/incubation.html#releases



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

2023-11-28 Thread tison
Thanks for your reference. Then it's not a blocker. Although I may
prefer name the folder as "apache-answer-1.2.0-incubating-src", it's
not required.

Restate +1 (binding)

Best,
tison.

Justin Mclean  于2023年11月28日周二 21:16写道:
>
> Hi,
>
> The release artefacts include incubating in their names [1] as Incubator 
> policy requires [2].
>
> Kind Regards,
> Justin
>
> 1. 
> https://dist.apache.org/repos/dist/dev/incubator/answer/1.2.0-incubating-RC1/
> 2. https://incubator.apache.org/policy/incubation.html#releases
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org