Release Metafacture core 5.4.0

[dr0i]

Next release following metafacture-core-5.3.2, HEAD at c8ecbdafac615c0dea92868513b456084f205dbf.

• [x] test release candidate
• [x] release on maven central
• [x] release on github
• [x] write blog post
• [x] write to email list

[dr0i]

@blackwinter and @fsteeg: Please test release candidate feature-5.4.0-rc1-SNAPSHOT , see https://github.com/metafacture/metafacture-core/wiki/Maintainer-Guidelines#consume-the-snapshot how to configure your build tool.

[blackwinter]

:+1: Ran both Metafix and Limetrans tests with RC1.

P.S.: The title says 5.4.1 - should be .0, right?

[fsteeg]

Tested in oersi-etl, metafacture-fix, and metafacture-playground, looks good :+1:.

[dr0i]

P.S.: The title says 5.4.1 - should be .0, right?

jepp! Fixed that.

[dr0i]

Maven release triggered. Github release ready, please have a look at the description https://github.com/metafacture/metafacture-core/releases/tag/metafacture-core-5.4.0 if anything is missing etc. This will be the base for the blog post.

[blackwinter]

:+1: Thanks!

[dr0i]

U-hu, one faux pas from my side: I said "head is at https://github.com/metafacture/metafacture-core/commit/c8ecbdafac615c0dea92868513b456084f205dbf" but in the meanwhile merged 2fa964a3e6b7fb322c1a599697542bd04b480dfd into master , and this got into the release. So this is not tested.

[blackwinter]

Are you saying it wasn't in the RC, but is in the release now? That's definitely not ideal.

The non-OAI-PMH use cases seem to be unaffected, though. Metafix and Limetrans tests still pass.

[dr0i]

Yep. Note to future self to take more care.

[fsteeg]

5.4.0 still looks good for oersi-etl, metafacture-fix, and metafacture-playground.

[dr0i]

All done. Closing.