I propose we release 3.8.0 soon. So far we have the following changes :
I would also add a follow-up CSS clean-up as suggested by @tfmorris here: Issue 6353 implement Windows ordering buttons ("OK" / "Cancel") by zyadtaha · Pull Request #6482 · OpenRefine/OpenRefine · GitHub
Are you aware of anything else that should go into such a release?
@Martin suggested we try to include support for advertising the survey and other events as well.
I have opened a PR for that here:
OpenRefine:master
← wetneb:6290-release-and-event-notifications
opened 06:56PM - 04 Apr 24 UTC
This also makes sure we first prompt the user before making a request to an exte… rnal web service.
Closes #6290. Closes #6017.
### How to test this PR
* To test the workflow of getting notified about a new release, change the `ASSIGNED_VERSION` in `main/src/com/google/refine/RefineServlet.java` from `3.9-SNAPSHOT` to some older version, such as `3.5.0`
* To test the workflow of getting notified about another sort of event, change `https://openrefine.org/versions` to `https://deploy-preview-316--openrefine-website.netlify.app/versions.json` in `main/webapp/modules/core/scripts/index.js`
### Screenshots



The CSS clean-up mentioned above ended up being more benign than I was expecting, so I would say it's not so critical to ship it in that release:
OpenRefine:master
← wetneb:recon_dialog_css_cleanup
opened 10:53AM - 29 Mar 24 UTC
Following up on
https://github.com/OpenRefine/OpenRefine/issues/6353#issuecomme… nt-2021092463.
The `button-left` and `button-right` classes are not used anywhere in the app. The `dialog-footer` class should not be styled by this file and the `display: flex` does not have any visible impact on dialogs as far as I can tell, so it looks safe to remove.
1 Like
I think it would also be worth including this:
OpenRefine:master
← wetneb:6257-jars-instead-of-classes
opened 10:12AM - 08 Apr 24 UTC
Closes #6257.
I tested running it both from the development version (`./refin… e` in a git clone) and from the packaged version on Linux. Let's see if the CI agrees.
I'd be tempted to include this in 3.8 but because it is likely that this breaks some things, I'd make it another beta instead of releasing 3.8.0 already.
Since it would be useful to @apo for Debian packaging.
Maybe we should do another beta then, as it's quite some new changes which will not have been tested much in master
. Should we make a "3.8-beta2" then?