Reconfiguration of bounce processing on this mailing list
by Sanne Grinovero
Hi all,
I reconfigured some details of Mailman regarding this list, following
advice from Red Hat sysadmins. This is unlikely to solve the problems
but should help us get some diagnostic data which is sadly missing at
this moment.
Please do not make any change, or reach out to me in case of such need.
Thanks,
Sanne
5 years, 5 months
Moderation of in.relation.to
by Sanne Grinovero
Apparently I stopped receiving notifications from Discus about needing
to approve a comment, and it looks like you all did?
I just noticed as someome mentioned "while my other comment is not
approved" and I thought "wait, what? I know nothing about other
pending comments.." and didn't see any clue on the UI either.
I eventually found the comments approval queue, and there were a dozen
comments waiting; some >8 months old. Embarassing :(
Let's make sure that at least some of us receive a timely
notification. Any volunteers to register for this? I will register
myself, hoping that some more of you will join on this.
Thanks,
Sanne
5 years, 5 months
Hibernate 5.2.18
by Guillaume Smet
Hi,
I started the release process but our Nexus' Lucene indexes are apparently
broken.
Can't close the repository and release it.
Will follow up next week.
--
Guillaume
5 years, 5 months
CI - Default Maven settings
by Yoann Rodiere
Hello,
Because of recurring issues, I will remove the default Maven settings that
include the JBoss Nexus coordinates from our CI.
Be prepared for build failures on Maven projects (I don't think Gradle
projects will be impacted), and please let me know if you can't solve them.
Generally a failing build can easily be fixed by adding "-s
settings-example.xml" to the Maven arguments, where "settings-example.xml"
is a file in your git repository that should be there for new contributors'
sake anyway.
There are also ways to get rid of the custom settings completely for
non-release builds, but that will require one or two days worth of work,
due to all the places in our builds relying on these settings (Karaf,
Wildfly, ...). If you are interested, just ping me and I can explain what
we did on Search.
As to why:
The idea is that anyone checking out our projects should be able to run
`mvn clean install` and it should "just work"; to check that, our CI builds
should be as similar as possible to a random contributor's environment,
i.e. it should be as little customized as possible.
With that in mind, having custom Maven settings applied by default to all
projects does not make much sense to me, and even seems harmful. In my case
it's harmful because I expected all the necessary configuration, including
the URL of the JBoss Nexus, to be included in Search's POM files, and I
expected the build to fail if anything was missing, allowing me to see that
Search is not contributor-friendly and should be fixed. As it turns out,
because of our CI, it was not the case.
Yoann Rodière
Hibernate NoORM Team
yoann(a)hibernate.org
5 years, 5 months
Hibernate ORM 5.4.0.CR1 released
by Guillaume Smet
Hi,
We just released Hibernate ORM 5.4.0.CR1, the first candidate release of
5.4.0.
5.4 is the direct continuation of 5.3 and we will encourage everyone to
upgrade to it to benefit from the latest fixes.
Thus thoroughly testing this release candidate is especially important.
It brings EntityGraph improvements, out of the box JDK 11 support, bug
fixes and other minor improvements.
More information in the announcement post:
http://in.relation.to/2018/11/15/hibernate-orm-540-cr1-out/ .
Feedback very welcome!
--
Guillaume
5 years, 5 months
JIRA self-registration of users
by Sanne Grinovero
Hi all,
I'm receiving requests to approve people who are creating accounts on JIRA.
While it's good to see lots of people interested in registering, I've
never had to approve these before.
Did someone change settings or should I report this to Atlassian?
Thanks,
Sanne
5 years, 5 months
ORM 5.4.0 release schedule
by Guillaume Smet
Hi,
We discussed the 5.4.0 release schedule with Gail and decided on the
following:
- Tomorrow Wednesday 6PM CET (e.g. Paris time): master is frozen, please
don't commit anything to master after this time. And please don't commit
anything without proper review.
- Tomorrow her time, Gail will run the TCK and the API checks - hopefully
it won't go too bad
- I'll release CR1 Thursday afternoon my time
Please don't commit anything to master after Wednesday 6PM CET (obviously
unless it fixes TCK tests or API issues).
Note that CR meaning candidate release, the idea is to not push anything
else until Final, except if we have reports from the fields.
I don't think it's worth creating a branch as we will have to backport
everything anyway so please refrain from merging anything until Final, once
CR1 is released.
Thanks everyone.
--
Guillaume
5 years, 5 months
