# OpenRefine 3.10 release timeline **URL:** \ **Category:** Development & Design\ **Created:** [April 28, 2025, 6:22pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267 "2025-04-28T18:22:07Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [April 28, 2025, 6:22pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/1 "2025-04-28T18:22:08Z")
Hi all, in the past it seems that we've tried to release a new minor version every six months or so. That would mean that we're approaching a good time to start the release process for OpenRefine 3.10 (while 3.9 was only released in February, 3.8 was released last April, so we'd average out to every 6 months). As for the release process, my impression is that this new minor version should include everything in the `master` branch at the time the beta release is created. Unless an objection is raised, I'll plan to create a beta release next week for users to test with. ---
**Author:** ![antonin\_d](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/antonin_d/32/32_2.png) [@antonin\_d](https://forum.openrefine.org/u/antonin_d)\ **Post date:** [April 29, 2025, 1:32pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/2 "2025-04-29T13:32:18Z")
Sounds very good! I'd be interested in getting [the PR for history visualization](https://github.com/OpenRefine/OpenRefine/pull/7196) merged before that, and am available to make any adjustments if needed 馃檪 ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [April 29, 2025, 1:38pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/3 "2025-04-29T13:38:46Z")
Yes, I'm hoping to merge a decent number of outstanding pull requests before the beta is out. This will be one of them! ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [May 13, 2025, 9:10pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/4 "2025-05-13T21:10:43Z")
Hi all, just a quick update: I pushed back releasing a beta version to later this week as I try to wrap up some remaining pull request reviews. I'll try to have everything ready by Friday so I can do the release during office hours! ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [May 16, 2025, 1:42pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/5 "2025-05-16T13:42:20Z")
Hi folks, since there's no rush to release 3.10, I'd like to propose pushing back the beta another week or two to let conversations around existing pull requests resolve. In addition to the aforementioned pull request about recipe visualization, there's also an open pull request for drag and drop column reordering. If anyone has features that they are eagerly awaiting, we can cut a point release in the meantime. ---
**Author:** ![abbe98](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/abbe98/32/1299_2.png) [@abbe98](https://forum.openrefine.org/u/abbe98)\ **Post date:** [June 10, 2025, 4:20pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/6 "2025-06-10T16:20:21Z")
Just want to jump in here to highlight the following regression on the master branch: [It's no longer possible to select column header text 路 Issue #7338 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/issues/7338) ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [June 13, 2025, 12:06am UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/7 "2025-06-13T00:06:37Z")
I'm trying to work through pull requests in preparation for releasing a 3.10 beta. In addition to the issue @abbe98 mentioned above, I'd at least like to get [fix storeBlankColumns: delete only after project parsed by smierz 路 Pull Request #7272 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/pull/7272) merged before releasing the beta. Please reach out if there are any other issues and/or pull requests you'd specifically like to see included in this release. In the meantime, I'll also be tagging unreleased PRs with the 3.10 milestone in GitHub. ---
**Author:** ![abbe98](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/abbe98/32/1299_2.png) [@abbe98](https://forum.openrefine.org/u/abbe98)\ **Post date:** [June 24, 2025, 8:32am UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/8 "2025-06-24T08:32:11Z")
FYI reviewing #7345 is on my radar and I hope to get to it soon. ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [June 24, 2025, 7:09pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/9 "2025-06-24T19:09:23Z")
Thanks! In terms of other PRs, I think we're ready to merge #7272 and I'd also like to volunteer to finish [feat: add mouse shortcuts to column headers by ntcho 路 Pull Request #7268 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/pull/7268) before releasing 3.10. ---
**Author:** ![tfmorris](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/tfmorris/32/17_2.png) [@tfmorris](https://forum.openrefine.org/u/tfmorris)\ **Post date:** [June 25, 2025, 6:27am UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/10 "2025-06-25T06:27:24Z")
I've reviewed and merged #7272. I think #7314 is a significant regression, so it would be good to address it. I've put up a non-minimal draft PR, which leans more heavily on Apache Commons Compress and which adds more of the formats that it supports (e.g. 7zip), that I'll try to clean up in the next day. If folks feel strongly that it should be limited to a minimal bug-fix only patch, I'm happy to consider reworking it. [https://github.com/OpenRefine/OpenRefine/pull/7353](https://github.com/OpenRefine/OpenRefine/pull/7353) I'll confess to not having carefully reviewed the rest of the outstanding issues, but if users haven't complained about them, then they probably aren't critical. Tom ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [July 2, 2025, 8:08pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/11 "2025-07-02T20:08:46Z")
In addition to reviewing #7353, I'm going to spend some time trying to test the master branch with a few of the extensions listed on the community page. My hope is that this will check for any major issues, such as an extension preventing OpenRefine from starting at all. If there are specific failure scenarios that people know about and would like me to check, please reach out! ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [August 7, 2025, 3:35pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/12 "2025-08-07T15:35:19Z")
Hey folks, just a quick update here. I鈥檇 like to make some progress on this in August. I鈥檒l have an update on [#7361](https://github.com/OpenRefine/OpenRefine/pull/7361) shortly. I鈥檒l also be reviewing [#7370](https://github.com/OpenRefine/OpenRefine/pull/7370) in hopes of including it in 3.10. @tfmorris, are you still hoping to finish [#7353](https://github.com/OpenRefine/OpenRefine/pull/7353) in time for the release? Is there anything I could help with? ---
**Author:** ![smierz](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/smierz/32/1713_2.png) [@smierz](https://forum.openrefine.org/u/smierz)\ **Post date:** [September 27, 2025, 3:24pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/13 "2025-09-27T15:24:00Z")
_fyi i noticed the discussion about 3.10 branched off into [Developer and Community Engagement update: September 2025](https://forum.openrefine.org/t/developer-and-community-engagement-update-september-2025/2579) so I wasn't sure where to put my answer, but I decided to use this main thread_ Wanted to add 2 suggestions for the GitHub 3.10 milestone label: - [uniform batch size handling for preview import (in db extension) 路 Issue #7444 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/issues/7444) - [Database import progress bar exceeds the intended 100% box 路 Issue #6654 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/issues/6654) About #7370 row sampling during import: I will need some time to get back and think about this, so it will probably not be finished soon-ish ---
**Author:** ![tfmorris](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/tfmorris/32/17_2.png) [@tfmorris](https://forum.openrefine.org/u/tfmorris)\ **Post date:** [November 25, 2025, 5:49pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/14 "2025-11-25T17:49:33Z")
> _fyi i noticed the discussion about 3.10 branched off into [Developer and Community Engagement update: September 2025](https://forum.openrefine.org/t/developer-and-community-engagement-update-september-2025/2579) so I wasn't sure where to put my answer, but I decided to use this main thread_ +1 for keeping the discussion here. On the other thread, Rory said (back at the end of September): > I saw the 3.10 milestone on GitHub, thank you for creating that. The only thing I鈥檇 like to add is the resolution to the drag and drop feature as discussed on #7345. Do we still want to try and include drag-and-drop in this release? I don't think it's a huge lift, but it seems blocked on a UX design proposal. We're getting to the time of year where the holidays are fast approaching and we're in danger of pushing into 2026 unless we start the beta process soon. There's nothing magical about the calendar year boundary, but it's a nice delimiter. I think some of the other issues currently targeted for 3.10 can be pushed out, but we need to figure out how to manage the V.next planning process, so that we have a milestone to push them to. As a straw horse, I'll propose the following: 1. rename the 4.0 milestone to something more representative of its historical role such as 4.0-proto (or perhaps "delta" which I think the branch was renamed) 2. create a new milestone called V.next for the next major release which doesn't have compatibility constraints 3. move open issues which are still relevant from 4.0-proto to V.next (or the backlog, if longer term goals). Close non-relevant open issues. 4. [the hard part] go through closed 4.0-proto issues and identify those which have been closed, but only merged to the 4.0/delta branch and not to master. Reopen these and move them to either V.next or the backlog. Only the first two steps (choosing names, in particular) are needed to enable moving issues out of 3.10. Tom ---
**Author:** ![tfmorris](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/tfmorris/32/17_2.png) [@tfmorris](https://forum.openrefine.org/u/tfmorris)\ **Post date:** [November 25, 2025, 7:03pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/15 "2025-11-25T19:03:49Z")
Actually, I missed that there's a design proposal in [https://github.com/SoryRawyer/OpenRefine/tree/grid-header-shortcuts](https://github.com/SoryRawyer/OpenRefine/tree/grid-header-shortcuts) I'll see if I can build and test it, but it probably needs to be in a more accessible form for others to review. Tom ---
**Author:** ![Martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/martin/32/7_2.png) [@Martin](https://forum.openrefine.org/u/Martin)\ **Post date:** [November 25, 2025, 8:03pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/16 "2025-11-25T20:03:49Z")
> [@tfmorris](#): > > rename the 4.0 milestone to something more representative of its historical role such as 4.0-proto (or perhaps "delta" which I think the branch was renamed) Yes, the proposition was to rename it `delta` in [How do we communicate the 4.0 branch with our users?](https://forum.openrefine.org/t/how-do-we-communicate-the-4-0-branch-with-our-users/1449) > [@tfmorris](#): > > Actually, I missed that there's a design proposal in [GitHub - SoryRawyer/OpenRefine at grid-header-shortcuts](https://github.com/SoryRawyer/OpenRefine/tree/grid-header-shortcuts) > > I'll see if I can build and test it, but it probably needs to be in a more accessible form for others to review. See @Rory update (and test build) here [Project grid header design - #2 by Rory](https://forum.openrefine.org/t/project-grid-header-design/2622/2) ---
**Author:** ![tfmorris](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/tfmorris/32/17_2.png) [@tfmorris](https://forum.openrefine.org/u/tfmorris)\ **Post date:** [November 25, 2025, 8:54pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/17 "2025-11-25T20:54:40Z")
> Yes, the proposition was to rename it `delta` in [How do we communicate the 4.0 branch with our users?](https://forum.openrefine.org/t/how-do-we-communicate-the-4-0-branch-with-our-users/1449) I've renamed the old milestone to delta as well and added a new V.next milestone. Everyone is welcome to help sorting through the issues. > > ![](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/tfmorris/48/17_2.png)tfmorris: > > > > Actually, I missed that there's a design proposal in [GitHub - SoryRawyer/OpenRefine at grid-header-shortcuts](https://github.com/SoryRawyer/OpenRefine/tree/grid-header-shortcuts) > > > > I'll see if I can build and test it, but it probably needs to be in a more accessible form for others to review. > > See [@Rory](https://forum.openrefine.org/u/rory) update (and test build) here [Project grid header design - #2 by Rory](https://forum.openrefine.org/t/project-grid-header-design/2622/2) Thanks for the heads up. Neither the forum nor Github PR edits made it into the email notification threads. I added a comment to the Github PR which will hopefully alert other followers to the screenshots. Tom ---
**Author:** ![smierz](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/smierz/32/1713_2.png) [@smierz](https://forum.openrefine.org/u/smierz)\ **Post date:** [November 26, 2025, 9:35am UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/18 "2025-11-26T09:35:30Z")
just a note about the relationship of issues: - fixing [uniform batch size handling for preview import (in db extension) 路 Issue #7444 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/issues/7444) - uncovered [db-extension: Preview does not load 100 rows, if batch size is smaller than 100 路 Issue #7499 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/issues/7499) - and then in both issues public code was removed instead of deprecated which was fixed in [Deprecate before delete by smierz 路 Pull Request #7528 路 OpenRefine/OpenRefine 路 GitHub](https://github.com/OpenRefine/OpenRefine/pull/7528) --\> so these are kind of a package deal because #7444 was added to the 3.10 milestone, I added the other two as well ---
**Author:** ![tfmorris](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/tfmorris/32/17_2.png) [@tfmorris](https://forum.openrefine.org/u/tfmorris)\ **Post date:** [November 26, 2025, 7:08pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/19 "2025-11-26T19:08:13Z")
> --\> so these are kind of a package deal > because #7444 was added to the 3.10 milestone, I added the other two as well Thanks. Everything that's been merged to master will go out when the 3.10 branch is cut, so there's no danger of missing anything. I'll sometimes add closed issues to a milestone to help remember to include it in the release notes, or for the historical record, but they're never in danger of getting missed. Open issues get added to / removed from milestones for planning purposes (and we, as a team, can always change our minds about the release contents at any time). Tom ---
**Author:** ![Rory](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.openrefine.org/rory/32/1517_2.png) [@Rory](https://forum.openrefine.org/u/Rory)\ **Post date:** [November 26, 2025, 7:54pm UTC](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267/20 "2025-11-26T19:54:23Z")
> [@tfmorris](#): > > Do we still want to try and include drag-and-drop in this release? I don't think it's a huge lift, but it seems blocked on a UX design proposal. I think it makes sense to work on a design and target the next release for drag-and-drop, so I've moved that to the V.next milestone. I think having the different milestones will help with release planning. Thank you for adding them @tfmorris. As for releasing a beta, I'd be happy to cut a 3.10 branch next week to start testing. It looks like the in-progress pull requests could be cherry-picked in if needed. [Next page](https://forum.openrefine.org/t/openrefine-3-10-release-timeline/2267.md?page=2)