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:
-- 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]
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
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
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
+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
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
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
[
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
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
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
+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
+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
13 matches
Mail list logo
