Yikun commented on PR #458: URL: https://github.com/apache/spark-website/pull/458#issuecomment-1522651856
> I believe 3.4.0 and v3.4.0 only causes many confusions to the users. In Apache Spark community, that's the reason why I propose to keep v3.4.0 tag format only (whatever we used; manual or GitHub) The reason of we remove `v` is to follow [DOI rules](https://github.com/docker-library/official-images#tags-and-aliases). If we still think `v` should be keep **in future**, we can both keep them (to point new images). > Given (1) and (2), I don't think this PR claims to maintain an existing manual publish process. In other words, this PR already burn the bridge. At this point, below might the solutions to continue the work: Solution 1: 1. Switch Java 17 to default in spark-docker: https://github.com/apache/spark-docker/pull/35 2. Keep v3.4.0 and 3.4.0 to point GA publish image. 3. Keep this PR to instead of manual process Solution 2: 1. Recover `latest` to manual publish image for 3.4.0 images. 2. Revert this PR (Recover the manual process and also keep the GA publish steps in this PR's doc) 3. `v3.4.0` point to manual image, `3.4.0` point to GA publish image 4. Keep manual image and GA publish image in 3.4.0 series, and unifed all images into GA publish image to in 3.5.0 @dongjoon-hyun @HyukjinKwon @zhengruifeng WDYT? -- 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, e-mail: commits-unsubscr...@spark.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org For additional commands, e-mail: commits-h...@spark.apache.org
