[GitHub] [spark-website] holdenk commented on pull request #400: [SPARK-39512] Document docker image release steps

2022-07-06 Thread GitBox
holdenk commented on PR #400: URL: https://github.com/apache/spark-website/pull/400#issuecomment-1176618299 ping @MaxGekk & @tgravescs @gengliangwang since y'all had comments on the first draft, this one looking ok? -- This is an automated message from the Apache Git Service. To respond

[GitHub] [spark-website] holdenk commented on pull request #400: [SPARK-39512] Document docker image release steps

2022-07-04 Thread GitBox
holdenk commented on PR #400: URL: https://github.com/apache/spark-website/pull/400#issuecomment-1174357233 My bad let me pick this up tomorrow. -- 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

[GitHub] [spark-website] holdenk commented on pull request #400: [SPARK-39512] Document docker image release steps

2022-06-25 Thread GitBox
holdenk commented on PR #400: URL: https://github.com/apache/spark-website/pull/400#issuecomment-1166205843 Sounds good. Want me to add the instructions to the RC step too then? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub

[GitHub] [spark-website] holdenk commented on pull request #400: [SPARK-39512] Document docker image release steps

2022-06-24 Thread GitBox
holdenk commented on PR #400: URL: https://github.com/apache/spark-website/pull/400#issuecomment-1166189409 Maybe, unlike maven repos though we don't have a staging location set up, I think we could ask ASF Infra to make us a staging location? -- This is an automated message from the