dongjoon-hyun opened a new pull request, #2176:
URL: https://github.com/apache/orc/pull/2176

   This PR aims to remove `Ubuntu 20.04` Support from Apache ORC 2.1.0.
   
   1. Remove from GitHub CIs
   2. Remove from `docker` directory
   3. Remove from Apache ORC Website.
   
   Apache ORC 2.1.0 is scheduled in 2025 and Ubuntu 20.04 LTS is going to reach 
the end of support April 2025. We had better focus on the latest OSes at Apache 
ORC 2.1.0.
   
   | Version | RELEASED | END OF STANDARD SUPPORT |
   | - | - | - |
   | Ubuntu 20.04 LTS (Focal Fossa) | Apr 2020 | Apr 2025 |
   
   Pass the CIs. However, it will pass because this is a removal of test 
coverage.
   
   No.
   
   Closes #1983 from dongjoon-hyun/ORC-1745.
   
   Authored-by: Dongjoon Hyun <dongj...@apache.org>
   
   (cherry picked from commit c29857a6acf0bea11672cc37e5da140daa3c483a)
   
   <!--
   Thanks for sending a pull request!  Here are some tips for you:
     1. File a JIRA issue first and use it as a prefix of your PR title, e.g., 
`ORC-001: Fix ABC`.
     2. Use your PR title to summarize what this PR proposes instead of 
describing the problem.
     3. Make PR title and description complete because these will be the 
permanent commit log.
     4. If possible, provide a concise and reproducible example to reproduce 
the issue for a faster review.
     5. If the PR is unfinished, use GitHub PR Draft feature.
   -->
   
   ### What changes were proposed in this pull request?
   <!--
   Please clarify what changes you are proposing. The purpose of this section 
is to outline the changes and how this PR fixes the issue. 
   If possible, please consider writing useful notes for better and faster 
reviews in your PR. See the examples below.
     1. If you refactor some codes with changing classes, showing the class 
hierarchy will help reviewers.
     2. If there is a discussion in the mailing list, please add the link.
   -->
   
   
   ### Why are the changes needed?
   <!--
   Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, you can clarify why it is a bug.
   -->
   
   
   ### How was this patch tested?
   <!--
   If tests were added, say they were added here. Please make sure to add some 
test cases that check the changes thoroughly including negative and positive 
cases if possible.
   If it was tested in a way different from regular unit tests, please clarify 
how you tested step by step, ideally copy and paste-able, so that other 
reviewers can test and check, and descendants can verify in the future.
   If tests were not added, please describe why they were not added and/or why 
it was difficult to add.
   -->
   
   ### Was this patch authored or co-authored using generative AI tooling?
   <!--
   If generative AI tooling has been used in the process of authoring this 
patch, please include the
   phrase: 'Generated-by: ' followed by the name of the tool and its version.
   If no, write 'No'.
   Please refer to the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) for details.
   -->
   


-- 
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: issues-unsubscr...@orc.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to