16.4.0 & 17.4.0 released, some quick comments

[rbygrave]

• A docker change around port detection broke ebean-test-containers. If you are seeing issues around the exposed port for test docker containers then it's likely that issue and bump ebean-test-containers to 8.0

• FYI: Maintaining the 2 branches for 16.x and 17.x is going well, no extra effort at the moment etc so no reason to stop doing that.

• AI impact? I believe that it's going to be very important to have good clear documentation on:
  (A) what good looks like
  (B) How to do ... (e.g. generate a db migration, setup testing etc).

In terms of "what good looks like", I'm now solidly in the camp that explicit programmatic configuration is preferrable over the configure from properties style (which is harder for folks to know how to adjust, more magical how it works etc). So things like this need a big uplift in terms of documentation and I think more explicit documentation is good to drive AI more accurately (e.g. How to use Lombok properly with Ebean, don't use Lombok @Data etc).

Also apologies for being slow to respond over the last period. I'm honestly feeling pretty optimistic that the rest of this year is going to see a nice uplift for Ebean. For some background, the avaje libraries, compile to native with graalvm native image etc is all going really really well but yeah that has taken some cycles out that would otherwise have gone into Ebean.

Cheers, Rob.