Am 2021-11-08 um 15:01 schrieb Mark Thomas:
On 05/11/2021 08:37, Mark Thomas wrote:
On 02/11/2021 16:58, Christopher Schultz wrote:
Mark,
On 11/2/21 07:45, Mark Thomas wrote:
Hi all,
There doesn't seem to be much in the changelogs at the moment and
the code signing is currently unavailable as the renewal process is
taking longer than expected. Therefore, my current thinking is to
delay the release process and review the situation towards the end
of the week.
Thoughts?
+1
I was thinking the same thing (not much to release).
The code signing service is now back up and running.
I'd like to configure the code signing service to use a certificate
that includes "Tomcat" in the name (currently we have a dedicated cert
for Tomcat but it names the ASF as a whole). That should be fairly quick.
I'd also like to iron out the wrinkles in the new CI service. As far
as I can tell, the Tomcat jobs have been migrated but there are a few
small issues to resolve.
I plan to work on the above today and - if make sufficient progress -
intend to tag towards the end of today although that might slip to
over the weekend / early next week.
The cert change is currently pending the request for new certificate
being approved by the CA. I think this can wait until next time.
The migrated BuildBot service is pretty much there. I need to update the
links on the web site, confirm the APR tests run correctly now the
native library is available on the worker and iron out any other wrinkles.
Good news! I am still considering to log a warning when a
LifecycleListener is used within a lifecycle object it is not intended
to run. As done wrong in Spring Boot with the AprLifecycleListener.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
