Skip to content
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

Release 2.1.0 #498

Open
4 of 9 tasks
olleolleolle opened this issue Jun 10, 2021 · 9 comments
Open
4 of 9 tasks

Release 2.1.0 #498

olleolleolle opened this issue Jun 10, 2021 · 9 comments
Assignees
Labels

Comments

@olleolleolle
Copy link
Member

olleolleolle commented Jun 10, 2021

This is a release management coordination issue for an upcoming release.

Version: 2.1.0 - a new minor since #491 dropped JRuby 9.0 support. And #499 dropped 9.1 support. #502 lost old vendored now-unused repositories. #503 Drop support for old versions.

TODO

Checklist before take-off:

@olleolleolle olleolleolle self-assigned this Jun 10, 2021
@deivid-rodriguez
Copy link
Contributor

Thanks @olleolleolle. Before a warbler release happens, I think there should also be releases of:

With those releases, we'll be able to get warbler's CI fully green (right now it claims it's green, but it's actually broken) and release with confidence.

@mkristian
Copy link
Member

mkristian commented Jun 12, 2021 via email

@deivid-rodriguez
Copy link
Contributor

@mkristian I think work was already done at jruby/jruby-maven-plugins#106, so it'd be a matter of releasing unless there's something obviously wrong there.

@olleolleolle
Copy link
Member Author

Added as checkboxes to tick, in the coordination progress list. Thanks for making that explicit, @deivid-rodriguez! And 👋 @mkristian, that's awesome!

@ioanatia
Copy link
Contributor

ioanatia commented Apr 6, 2022

Any news on the new release? Do you need any help with it? 😄

@olleolleolle
Copy link
Member Author

@ioanatia One thing that would be good is to format changelog lines explaining what's is in the release. That can be done by anyone, in a PR.

@olleolleolle
Copy link
Member Author

Thanks to @nbekirov, we now have a section in History.txt, so that's ✅ too.

The jbundler repo seems untouched since last May. That repo does not have a running CI, currently. Perhaps that needs ❤️ ?

@kares
Copy link
Member

kares commented Jan 23, 2023

Not sure jbundler is relevant that much these days, as jar_dependencies is likely it's successor (bundled with JRuby).

But yeah ❤️ needed either way 😉

@olleolleolle
Copy link
Member Author

Not sure jbundler is relevant that much these days, as jar_dependencies is likely it's successor (bundled with JRuby).

Aha, TIL.

Does warbler need to change anything to take advantage of this New And Included thing? Or does it mostly mean "we are unencumbered by jbundler's release schedule"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants