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.
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!
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.
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 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.
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
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.
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!
