Status of release 1.5

[Sebastian Nagel]

Hi everybody,

the release artifacts of crawler-commons 1.5 are ready to publish.

Change log:

https://github.com/crawler-commons/crawler-commons/blob/crawler-commons-1.5/CHANGES.txt

Git tag:

https://github.com/crawler-commons/crawler-commons/releases/tag/crawler-commons-1.5

However, after the migration from Sonatype OSSRH to Central Portal (#510 [1])
it seems that there is no public staging repository available anymore.
The deployed staging artifacts are private for me (eventually, also Julien
is able to inspect them). Or did I miss something?

I'm not sure how to proceed with the vote because without a public staging
repository, nobody else can verify and test the release artifacts.

So far, I've
- verified the artifacts (checksums)
- tested the 1.5 jar for any regressions in robots.txt and sitemap parsing
on a large set of robots.txt / sitemap files

I'm happy to press the "Publish" button and perform the remaining steps.
But I'll wait for your comments and any objections to continue.

Aécio already suggested in #516 to simplify and automatize the release process.
We should definitely. It's quite a long task list [3] and it's easy to forget
a step.


Thanks and best,
~Sebastian


[1] https://github.com/crawler-commons/crawler-commons/issues/510
[2]
https://github.com/crawler-commons/crawler-commons/pull/516#pullrequestreview-2910196105
[3]
https://github.com/crawler-commons/crawler-commons/wiki/Step-by-step-guide-to-generating-a-release