[ 
https://issues.apache.org/jira/browse/SPARK-50089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hyukjin Kwon resolved SPARK-50089.
----------------------------------
    Resolution: Invalid

Resolving as Invalid: this is a usage/how-to question rather than a report of a 
specific Spark defect or a concrete change proposal. Apache Spark uses JIRA to 
track bugs and improvements; usage questions are best asked on the 
[email protected] mailing list (https://spark.apache.org/community.html) or 
Stack Overflow (tag apache-spark), where a wider audience can help. Please 
re-open with a concrete reproducer or a specific proposed code/doc change if 
this is actually a bug or an actionable improvement. Thanks!

> Clarification regarding Spark v3.4 and EOL status
> -------------------------------------------------
>
>                 Key: SPARK-50089
>                 URL: https://issues.apache.org/jira/browse/SPARK-50089
>             Project: Spark
>          Issue Type: Question
>          Components: Documentation
>    Affects Versions: 3.4.3
>            Reporter: Mark
>            Priority: Major
>
> Hi there.
> I'd like to enquire the current support status of Spark v3.4. The versioning 
> policy documentation, states that releases are typically supported for 18 
> months, and the last minor release is considered LTS and supported for longer.
> At the time of writing, there appears to be three versions of Apache Spark, 
> which are being built, and have release tags cut in GitHub:
>  * *v4.0 (preview, not GA)*
>  * *v3.5.x*
>  * *v3.4.x*
> +Could you help me determine how long v3.4.x is supported for?+ It still 
> looks to be active and I see -rc tags being cut in advance of the next v3.4x 
> patch release.
> I'd also like to work with 
> [endoflife.date|https://endoflife.date/apache-spark], to make the necessary 
> updates to v3.4. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to