is there a new version release plan? #2545
Comments
|
same question, there are a number of bug fixes that haven't made it out yet that are causing issues. |
|
Hi @nanmobei and @cmcnicholas. Thanks for getting in touch. We're gearing up to a v7 release and there are a couple of alphas available - 7.0.0-alpha.2 is the latest. Want to try one of those to see if they help? Otherwise please add a thumbs up to any existing issues that affect you so we know what to prioritise. |
|
@smallsaucepan I've been following the discussion around the upcoming v7 release since several months. I appreciate the efforts put into addressing the issues and improvements for Turfjs. Could you please provide an update on the progress of v7? Have most of the identified issues been resolved in the alpha versions, and is there a tentative timeline for preparing a final release? Or are there still open concerns that might affect the release timeline? Understanding the current status and potential ETA for v7 would greatly help in planning for those of us relying on Turfjs for our projects. Thank you for your continuous work on this valuable project. |
|
My opinion. We need more testers of the alphas. Would you be willing to give it a try and report back any issues? That's the best thing people watching and waiting can do. The Changelog should be up to date to get familiar with. I would say there is not a release plan. The work to be done is still somewhat fluid (growing/changing) and at the discretion of the few active contributors. It's a major release with breaking changes and the desire is to spend the time on getting known high value breaking changes in now. And a lot of typescript migration and dependency upgrades. I don't think there's anything pressing the release to get done. You can follow the active v7 discussions. New 6.x releases with fixes before v7 is a known thing that people want but should not be expected. |
|
Hi @3zzy, @cmcnicholas and @nanmobei. Have taken on board your comments, and chatted with the rest of the team about when we can get v7 out. As Tim mentioned fixing high value bugs is always desirable. However we do need to balance that against how long our users have been waiting for an official update. What I've proposed is we knock over a couple more maintenance PRs, and release alpha 3. If there aren't any major new issues arising out of that after a few weeks, we cut a v7 release. Hopefully once v7 is out the door we can return to fixing bugs one at a time. If anything requires a breaking change we backlog it until v8, and release that sometime next year. Hope that aligns with what you are hoping for! Quietly, I'm hoping we could v7 done by the end of the month. |
|
@smallsaucepan Thanks for the update! I fully support the plan. When I asked for an update, it was with the understanding that a release had to be cut at some point, especially since v7 has been in the works for months. I'd be glad to assist with testing at least and bug fixes where I can. |
|
Hi @smallsaucepan, thanks for a clear answer. Is there a chance the alphas could be coming out more frequently? There has been so many fixes (including the one I am waiting for) in the last three months and they would deserve more frequent updates. If it's too expensive to create a new version, could you please direct me to how I can use the current |
|
Hi @maral. Each merged PR now generates a new alpha release. Currently alpha 110 is the latest: https://www.npmjs.com/package/@turf/turf/v/7.0.0-alpha.110 That's probably your easiest way to keep up with the latest changes. Also helps us if you do and report any issues you see. |
Thanks very much for this, updated to alpha, will keep an eye out for any issues 👍 |
as the tittle say ,the new version(v6.5.0) has released 2 years ago ,is there a new version release plan?
The text was updated successfully, but these errors were encountered: