Release 2.1.0

[olleolleolle]

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:

• See Migrate CI to Github Actions #497 merged: GitHub Actions as CI
• v2.0.5...master look through, and find items for History.txt
• Jbundler, to allow bundler 2: https://github.com/mkristian/jbundler. Release jbundler new version with bundle support version >= 2 jbundler#102
• Jruby-maven-plugins, to support jruby >= 9.2.10: https://github.com/torquebox/jruby-maven-plugins
• Follow up with a rake build from a maintainer  #529
• Thank everyone
• Check and update the release instructions (add a link in this Issue)
• Check in with stakeholders that have done this before
• (Add more here!)

[deivid-rodriguez]

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

• Jbundler, to allow bundler 2: https://github.com/mkristian/jbundler.
• Jruby-maven-plugins, to support jruby >= 9.2.10: https://github.com/torquebox/jruby-maven-plugins

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]

I can take care if the jruby-maven-plugins as I prepared a branch already a while ago

[deivid-rodriguez]

@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]

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

[ioanatia]

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

[olleolleolle]

@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]

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]

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]

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"?

[dub357]

Can we get some movement on this?

[drzaiusx11]

as of right now it seems like Warbler is unusable on jruby 10 without this release, anything we can do to get this out?

[chadlwilson]

@drzaiusx11 a deployed warbler war won't actually work using Jruby 10 in the real world until jruby-rack 1.3 released anyway - because 1.2 depends on removed JRuby classes.

The tests here are probably a bit misleading - haven't investigated but am guessing they don't actually run traffic through a real servlet container.

There's likely a difference between being able to use this to created a warbled war using a and to have that war bundle -and-work-with- a given JRuby version.

But ya, a release and more love (and issue triage) is still desperately needed.

[drzaiusx11]

I managed to make due with my own jar creation script for now. I'll revisit should a release actually happen