Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc2

2023-11-15 Thread Felix Cheung
+1 binding

- incubating in name
- signature and hash fine
- DISCLAIMER is fine
- LICENSE and NOTICE are fine
- No unexpected binary files
- All source files have ASF headers

what is this file config-ui/.yarn/releases/yarn-3.4.1.cjs - seems to have
code in it (and it does not have a license header)


On Wed, Nov 15, 2023 at 6:17 AM Willem Jiang  wrote:

> +1(binding).
>
> Here is what I checked:
> - The checksums and signatures are validated.
> - The LICENSE and NOTICE files look good to me.
> - There is a DISCLAIMER file about incubating.
> - No binary files in the source release.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Fri, Nov 10, 2023 at 10:28 PM Zikuan An  wrote:
> >
> > Hello everyone,
> >
> > This is a call for the vote to release Apache DevLake (Incubating)
> > v0.19.0-rc2.
> > The Apache DevLake community has voted on and approved a proposal to
> > release Apache DevLake (Incubating) version v0.19.0-rc2.
> >
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Community vote thread:
> >
> > https://lists.apache.org/thread/zqhrctqz39xyslfjsd0zz30gtdbv4t20
> >
> >
> > Community vote result thread:
> >
> > https://lists.apache.org/thread/g06ns1vbqopyw6r460m25pvcvwh932s6
> >
> >
> > The release candidates:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc2
> >
> >
> > Git tag for the release:
> >
> > https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc2
> >
> >
> > Keys to verify the Release Candidate:
> >
> > https://downloads.apache.org/incubator/devlake/KEYS
> >
> >
> > How to build:
> >
> > https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
> >
> >
> > The vote will be open for at least 72 hours or until the necessary number
> > of votes is reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> >
> > Thanks
> >
> > Zikuan An
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


Re: [VOTE] Release Apache DevLake (Incubating) v0.19.0-rc2

2023-11-15 Thread Willem Jiang
+1(binding).

Here is what I checked:
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER file about incubating.
- No binary files in the source release.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Nov 10, 2023 at 10:28 PM Zikuan An  wrote:
>
> Hello everyone,
>
> This is a call for the vote to release Apache DevLake (Incubating)
> v0.19.0-rc2.
> The Apache DevLake community has voted on and approved a proposal to
> release Apache DevLake (Incubating) version v0.19.0-rc2.
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Community vote thread:
>
> https://lists.apache.org/thread/zqhrctqz39xyslfjsd0zz30gtdbv4t20
>
>
> Community vote result thread:
>
> https://lists.apache.org/thread/g06ns1vbqopyw6r460m25pvcvwh932s6
>
>
> The release candidates:
>
> https://dist.apache.org/repos/dist/dev/incubator/devlake/0.19.0-incubating-rc2
>
>
> Git tag for the release:
>
> https://github.com/apache/incubator-devlake/releases/tag/v0.19.0-rc2
>
>
> Keys to verify the Release Candidate:
>
> https://downloads.apache.org/incubator/devlake/KEYS
>
>
> How to build:
>
> https://devlake.apache.org/docs/DeveloperManuals/DeveloperSetup
>
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes is reached.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
>
> Thanks
>
> Zikuan An

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



Re: [VOTE] Release Apache OpenDAL(incubating) v0.42.0-rc.3 - Incubator Vote Round 1

2023-11-15 Thread Willem Jiang
+1 binding.

I checked
- incubating in the release kit name
- The checksums and signatures are validated.
- The LICENSE and NOTICE files look good to me.
- There is a DISCLAIMER in the release kits
- No binary files in the source release kits


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Nov 12, 2023 at 10:12 AM Mingzhuo Yin  wrote:
>
> Hello Incubator PMC,
>
> The Apache OpenDAL community has voted and approved the release of Apache
> OpenDAL(incubating) v0.42.0-rc.3. We now kindly request the IPMC members
> review and vote for this release.
>
> OpenDAL is a data access layer that allows users to easily and efficiently
> retrieve data from various storage services in a unified way.
>
> OpenDAL community vote thread:
>
> https://lists.apache.org/thread/2gqd6pm1k0cc1j0lq79d4ply721dmky2
>
> Vote result thread:
>
> https://lists.apache.org/thread/z8pv6c5rdv5ohn4fcgk4n40n9cfxtwdp
>
> The release candidate:
>
> https://dist.apache.org/repos/dist/dev/incubator/opendal/0.42.0-rc.3/
>
> This release has been signed with a PGP available here:
>
> https://downloads.apache.org/incubator/opendal/KEYS
>
> Git tag for the release:
>
> https://github.com/apache/incubator-opendal/releases/tag/v0.42.0-rc.3
>
> Maven staging repo:
>
> https://repository.apache.org/content/repositories/orgapacheopendal-1018/
>
> Please download, verify, and test.
>
> The VOTE will be open for at least 72 hours and until the necessary
> number of votes are reached.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> To learn more about apache opendal, please see https://opendal.apache.org/
>
> Checklist for reference:
>
> [ ] Download links are valid.
> [ ] Checksums and signatures.
> [ ] LICENSE/NOTICE files exist
> [ ] No unexpected binary files
> [ ] All source files have ASF headers
> [ ] Can compile from source
>
> More detailed checklist please refer to:
> https://github.com/apache/incubator-opendal/tree/main/scripts
>
> To compile from source, please refer to:
> https://github.com/apache/incubator-opendal/blob/main/CONTRIBUTING.md
>
> Here is python script in release to help you verify the release candidate:
>
> ./scripts/verify.py
>
> Thanks
>
> Sincerely,
> Mingzhuo Yin

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



[CANCEL][VOTE] Release Apache Answer, Incubating, v1.2.0

2023-11-15 Thread LinkinStar
Hi,

Thanks for the suggestion PJ, I'll start with some directory structure
adjustments based on his suggestions. So cancel the incubator vote and to
concentrate on starting a discussion thread on d...@answer.apache.org with
the new v1.2.0-RC1 version.

Thanks,
LinkinStar


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

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

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 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,  
general@incubator.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 4:12:18 EST,  general@incubator.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, Nov 15, 2023 at 4:08:16 EST,  general@incubator.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 [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,  general@incubator.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/
 [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 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 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 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



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

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


[jira] [Commented] (INCUBATOR-280) Datalab retired, but cleanup is incomplete

2023-11-15 Thread Sebb (Jira)


[ 
https://issues.apache.org/jira/browse/INCUBATOR-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17786220#comment-17786220
 ] 

Sebb commented on INCUBATOR-280:


The Incubator PMC is ultimately responsible. Some parts have to be done by 
Infra on request from the IPMC.

> Datalab retired, but cleanup is incomplete
> --
>
> Key: INCUBATOR-280
> URL: https://issues.apache.org/jira/browse/INCUBATOR-280
> Project: Incubator
>  Issue Type: Task
>Reporter: Sebb
>Priority: Major
>
> As the subject says



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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