[GitHub] [spark-website] dongjoon-hyun commented on pull request #458: Update Spark Docker Images publish workflow

2023-04-25 Thread via GitHub
dongjoon-hyun commented on PR #458: URL: https://github.com/apache/spark-website/pull/458#issuecomment-1522655970 @Yikun . We cannot simply remove anything like this PR. The official way to adopt new standard is to send the email on dev mailing list and build a community consensus.

[GitHub] [spark-website] dongjoon-hyun commented on pull request #458: Update Spark Docker Images publish workflow

2023-04-25 Thread via GitHub
dongjoon-hyun commented on PR #458: URL: https://github.com/apache/spark-website/pull/458#issuecomment-1522621830 1. If we are going to maintain the manual process, why do you remove old description in this PR? > For tag, it's intentional. In 3.4.0, v3.4.0 tag and 3.4.0 serious tags will

[GitHub] [spark-website] dongjoon-hyun commented on pull request #458: Update Spark Docker Images publish workflow

2023-04-25 Thread via GitHub
dongjoon-hyun commented on PR #458: URL: https://github.com/apache/spark-website/pull/458#issuecomment-1522543950 It's already Java 17 by default. > For java17, I think we can switch to java17 in docker image. -- This is an automated message from the Apache Git Service. To respond t

[GitHub] [spark-website] dongjoon-hyun commented on pull request #458: Update Spark Docker Images publish workflow

2023-04-25 Thread via GitHub
dongjoon-hyun commented on PR #458: URL: https://github.com/apache/spark-website/pull/458#issuecomment-1522426433 cc @sunchao , too -- 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 co

[GitHub] [spark-website] dongjoon-hyun commented on pull request #458: Update Spark Docker Images publish workflow

2023-04-25 Thread via GitHub
dongjoon-hyun commented on PR #458: URL: https://github.com/apache/spark-website/pull/458#issuecomment-1522426236 Hi, @Yikun , @HyukjinKwon , @yaooqinn , @zhengruifeng . it seems that this PR introduced two user-facing breaking changes - Downgrade Java from 17 to 11 ``` $ do