Re: [DISCUSS] Versionless Spark Programming Guide Proposal

My personal opinion is that having the documents per version (current and previous), without fixing previous versions - just keeping them as a snapshot in time of the current documentation once the new version was released, should be good enough. Because now Neil would like to change the documenta

Re: [DISCUSS] Versionless Spark Programming Guide Proposal

I will let Neil and Matt clarify the details because I believe they understand the overall picture better. However, I would like to emphasize something that motivated this effort and which may be getting lost in the concerns about versioned vs. versionless docs. The main problem is that some of

Re: [DISCUSS] Versionless Spark Programming Guide Proposal

Hi, Versioned documentation has the benefit that users can have reasonable confidence that features, functionality and examples mentioned will work with that released Spark version. A versionless guide runs into potential issues with deprecation, behavioral changes and new features. My concern

Re: [DISCUSS] Versionless Spark Programming Guide Proposal

I am +1 on this but as you guys mentioned, we should really be clear on how to address different versions. On Wed, 5 Jun 2024 at 18:27, Matthew Powers wrote: > I am a huge fan of the Apache Spark docs and I regularly look at the > analytics on this page >