-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automate release process #117
Comments
Thinking out loud. Why don't we merge Butterfly with OpenRefine at this point? |
It's definitely a possibility… I guess the only downside I can think of is that it would be making the OpenRefine repo a bit bigger (with longer build times, and so on) but arguably it would be a more faithful representation of the reality, letting us upgrade dependencies only once and use the same release schedule. @tfmorris thoughts? |
I support automated publishing of releases, but bundling seems to go counter to recent moves towards finer grained modularity (and discussion of replacing Butterfly's module system). Logically Butterfly and OpenRefine are very different things. |
I'm not suggesting that the modules should be merged or the logic itself, but rather the code repositories and releases. No more waiting for Butterfly merges/releases, no more separated pull requests, etc. |
At the moment, publishing a release on GitHub will not automatically upload artifacts to Maven Central.
We could set up a GitHub Actions workflow to take care of that.
See: OpenRefine/OpenRefine#6185
The text was updated successfully, but these errors were encountered: