Re: Apache YuniKorn (Incubating) - Community Graduation Vote

Hi Wilfred Adding a security@ mailing list sounds like a good idea, but I do not think that is required in the current stage. We can do that post-graduate. For now, the Apache security doc said > We strongly encourage you to report potential security vulnerabilities to one of our private

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

The private@ is a moderated list. This has two issues: a moderator needs to approve any message not sent by a PMC member. This will slow down the process of interaction with the reporter. It would also not reach the YuniKorn committers group as not all committers are part of the PMC. Security

[GitHub] [incubator-yunikorn-release] yuchaoran2011 merged pull request #61: [YUNIKORN-1006] add notes about incompatible changes in the release doc

yuchaoran2011 merged pull request #61: URL: https://github.com/apache/incubator-yunikorn-release/pull/61 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe,

[GitHub] [incubator-yunikorn-release] yangwwei commented on pull request #61: [YUNIKORN-1006] add notes about incompatible changes in the release doc

yangwwei commented on pull request #61: URL: https://github.com/apache/incubator-yunikorn-release/pull/61#issuecomment-1009612129 thanks for the quick review @yuchaoran2011 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [incubator-yunikorn-release] yuchaoran2011 commented on a change in pull request #61: [YUNIKORN-1006] add notes about incompatible changes in the release doc

yuchaoran2011 commented on a change in pull request #61: URL: https://github.com/apache/incubator-yunikorn-release/pull/61#discussion_r781765608 ## File path: docs/release-procedure.md ## @@ -74,6 +74,13 @@ Follow these steps to generate the list: - Select the style `Text`

[jira] [Resolved] (YUNIKORN-1006) Address QU 30, 40, 50

[ https://issues.apache.org/jira/browse/YUNIKORN-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chaoran Yu resolved YUNIKORN-1006. -- Resolution: Done > Address QU 30, 40, 50 > - > > Key:

[GitHub] [incubator-yunikorn-release] yangwwei opened a new pull request #61: [YUNIKORN-1006] add notes about incompatible changes in the release doc

yangwwei opened a new pull request #61: URL: https://github.com/apache/incubator-yunikorn-release/pull/61 Fix QU40 The project puts a high priority on backwards compatibility and aims to document any incompatible changes and provide tools and documentation to help users transition

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

Good point, let's get that fixed as well during the preparation. Thanks for the input! On Mon, Jan 10, 2022 at 7:25 PM Wilfred Spiegelenburg wrote: > Yes, that is the jira. It has been an issue for a long time. All repos > are stuck on a commit from January 2021. > Not sure what changed at that

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

Yes, that is the jira. It has been an issue for a long time. All repos are stuck on a commit from January 2021. Not sure what changed at that point but it looks like it is linked to the change from YUNIKORN-531, the move to github actions. Wilfred On Tue, 11 Jan 2022 at 14:07, Chaoran Yu wrote:

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

I agree. It makes PR reviews really hard. Is this the JIRA for it https://issues.apache.org/jira/browse/YUNIKORN-583? On Mon, Jan 10, 2022 at 7:04 PM Sunil Govindan wrote: > Yes, Chenya. > I found that very troubling as well. > > We have to clean that up. Thanks for chiming in. > > Thanks >

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

Yes, Chenya. I found that very troubling as well. We have to clean that up. Thanks for chiming in. Thanks Sunil On Mon, Jan 10, 2022 at 6:57 PM Chenya Zhang wrote: >  > > Another thing in my mind is our PR code check... :D > > The "check warning" from Codecov is everywhere which makes our PR

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

 Another thing in my mind is our PR code check... :D The "check warning" from Codecov is everywhere which makes our PR review inconvenient. I'm not sure if the ASF board will randomly check our PRs and find it not ideal. If there is no ticket tracking this, I could help to create one and do

[GitHub] [incubator-yunikorn-release] yuchaoran2011 commented on a change in pull request #60: [YUNIKORN-941] Split scheduler and admission controller deployments

yuchaoran2011 commented on a change in pull request #60: URL: https://github.com/apache/incubator-yunikorn-release/pull/60#discussion_r781708459 ## File path: helm-charts/yunikorn/templates/admission-controller-deployment.yaml ## @@ -0,0 +1,91 @@ +# +# Licensed to the Apache

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

I created YUNIKORN-1007 We have to look at LC20 more closely given the public artifacts that we have. + @Wilfred Spiegelenburg Thanks Sunil On Mon, Jan 10, 2022 at 11:59 AM Chenya Zhang wrote: > Thanks Weiwei for creating the tickets! I

[jira] [Created] (YUNIKORN-1007) LC20 For Docker Repo

Sunil G created YUNIKORN-1007: - Summary: LC20 For Docker Repo Key: YUNIKORN-1007 URL: https://issues.apache.org/jira/browse/YUNIKORN-1007 Project: Apache YuniKorn Issue Type: Sub-task

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

Thanks Weiwei for creating the tickets! I will help to work on https://issues.apache.org/jira/browse/YUNIKORN-1006 to address QU 30, 40, 50. On Mon, Jan 10, 2022 at 10:21 AM Weiwei Yang wrote: > I think we can add some documents to clearly address QU 30, 40, 50. > I have created a task under

[GitHub] [incubator-yunikorn-release] craigcondit opened a new pull request #60: [YUNIKORN-941] Split scheduler and admission controller deployments

craigcondit opened a new pull request #60: URL: https://github.com/apache/incubator-yunikorn-release/pull/60 Contains deployment changes to support the k8shim changes for YUNIKORN-941. -- This is an automated message from the Apache Git Service. To respond to the message, please log on

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

I think we can add some documents to clearly address QU 30, 40, 50. I have created a task under YUNIKORN-1005 to address them. Thank you Chenya, Holden for your feedback, please comment more if there is anything else outstanding. On Mon, Jan

[jira] [Created] (YUNIKORN-1006) Address QU 30, 40, 50

Weiwei Yang created YUNIKORN-1006: - Summary: Address QU 30, 40, 50 Key: YUNIKORN-1006 URL: https://issues.apache.org/jira/browse/YUNIKORN-1006 Project: Apache YuniKorn Issue Type: Sub-task

[jira] [Created] (YUNIKORN-1005) [Umbrella] Prepare graduation from ASF incubator

Weiwei Yang created YUNIKORN-1005: - Summary: [Umbrella] Prepare graduation from ASF incubator Key: YUNIKORN-1005 URL: https://issues.apache.org/jira/browse/YUNIKORN-1005 Project: Apache YuniKorn

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

For "The project provides a well-documented, secure and private channel to report security issues, along with a documented way of responding to them.' the standard that I've seen used is to tell people to e-mail private@ when they think they might have a security related issue. I think that would

Re: Apache YuniKorn (Incubating) - Community Graduation Vote

Hi Weiwei, Thanks for driving this! The evaluation is quite comprehensive overall. I checked our Apache project maturity guidelines and noticed the below three items. Not sure if we already have them but they are not blockers to our graduation. We could think more about them along the way. QU30

Apache YuniKorn (Incubating) - Community Graduation Vote

Hi YuniKorn community and mentors Based on the discussion thread [1], after 2 years time of incubating, it is considered that now is a good time to graduate YuniKorn from the ASF incubator and become a top-level Apache project. We have reviewed the ASF project maturity model [2] and provided some