You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by "andygrove (via GitHub)" <gi...@apache.org> on 2023/02/13 21:38:03 UTC

[GitHub] [arrow-datafusion] andygrove opened a new issue, #5269: Discuss release cadence / patch releases / LTS

andygrove opened a new issue, #5269:
URL: https://github.com/apache/arrow-datafusion/issues/5269

   **Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
   
   - We release a major DataFusion version with breaking changes every two weeks.
   - This creates work for downstream projects.
   
   **Describe the solution you'd like**
   
   - In parallel with the frequent major releases, offer "long-term support" for one major version for an extended period (perhaps three months?).
   - This would allow downstream projects to pick up bug fixes and performance improvements without much work and then schedule major upgrades once per quarter.
   - Other projects can upgrade every two weeks if they wish to.
   
   **Describe alternatives you've considered**
   Keep things as they are.
   
   **Additional context**
   
   


-- 
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: github-unsubscribe@arrow.apache.org.apache.org

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


[GitHub] [arrow-datafusion] alamb commented on issue #5269: Discuss release cadence / patch releases / LTS

Posted by "alamb (via GitHub)" <gi...@apache.org>.
alamb commented on issue #5269:
URL: https://github.com/apache/arrow-datafusion/issues/5269#issuecomment-1429857830

   I would be in favor of a LTS branch for sure -- the thing that is needed is the maintainer bandwidth to manage it (for example, to backport API compatible changes)
   
   cc @maxburke 


-- 
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: github-unsubscribe@arrow.apache.org

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


[GitHub] [arrow-datafusion] tustvold commented on issue #5269: Discuss release cadence / patch releases / LTS

Posted by "tustvold (via GitHub)" <gi...@apache.org>.
tustvold commented on issue #5269:
URL: https://github.com/apache/arrow-datafusion/issues/5269#issuecomment-1428746601

   Is there a risk this would encourage people to only update once every 3 months? I'm not sure we're at a level of API stability where performing 3 months of upgrades in one go wouldn't be a fraught experience?


-- 
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: github-unsubscribe@arrow.apache.org

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


[GitHub] [arrow-datafusion] andygrove commented on issue #5269: Discuss release cadence / patch releases / LTS

Posted by "andygrove (via GitHub)" <gi...@apache.org>.
andygrove commented on issue #5269:
URL: https://github.com/apache/arrow-datafusion/issues/5269#issuecomment-1428747966

   > Is there a risk this would encourage people to only update once every 3 months? I'm not sure we're at a level of API stability where performing 3 months of upgrades in one go wouldn't be a fraught experience?
   
   Yes, that is definitely a risk.


-- 
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: github-unsubscribe@arrow.apache.org

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