I'd like to deploy the Internationalization work (with Spanish and French translations) and other assorted updates (jquery 3.x -> 3.5.1 for all previewers, minor/additions corrections to the README.)
When this PR is merged, all Dataverse instances using the hosted previewers (as recommended/explained in the README) will automatically start using the updated code, although admins will have to re-register the previewers to get Internationalization to work. The fact that the changes go live immediately is what's different from a PR for non-hosted code.
Assuming no review issues to the content of the PR itself, I propose the following:
send an email to the community announcing the upcoming merge with a ~week notice that includes info on how to re-register (also in the readme)
merge
create a 1.1 release from the newly merged master branch
(FWIW: If there were any new functionality that turns on immediately, I'd suggest a longer notice period but this should just change the jquery used and nothing else will change unless/until an admin re-registers).
Is there anything else that should be done as part of this?
Thanks. I think the code itself has been reviewed/reasonably tested already as we merged it into the dev branch, so I mostly wanted feedback on the release process.
I'd like to deploy the Internationalization work (with Spanish and French translations) and other assorted updates (jquery 3.x -> 3.5.1 for all previewers, minor/additions corrections to the README.)
When this PR is merged, all Dataverse instances using the hosted previewers (as recommended/explained in the README) will automatically start using the updated code, although admins will have to re-register the previewers to get Internationalization to work. The fact that the changes go live immediately is what's different from a PR for non-hosted code.
Assuming no review issues to the content of the PR itself, I propose the following: send an email to the community announcing the upcoming merge with a ~week notice that includes info on how to re-register (also in the readme) merge create a 1.1 release from the newly merged master branch
(FWIW: If there were any new functionality that turns on immediately, I'd suggest a longer notice period but this should just change the jquery used and nothing else will change unless/until an admin re-registers).
Is there anything else that should be done as part of this?