DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
Overview
TBD
Ideas list
- Robustness improvements
- Review use of
System.currentTimeMillis()and switch toSystem.nanoTime()to improve robustness against wall clock jumps
See https://github.com/apache/tomcat/commit/a7d9a049bd081d4e3520aa796d7d5324a0bf258d for an example
- Review use of
- Code Quality (we'll need to export issues / provide attendees with access closer to the event)
- Open Coverity scan issues
- Open GitHub scan issues
- HTTP/2
- HTTP/2 clients not ACK'ing settings
- HTTP/2 clients not responding to PING
- Look at HTTP/2 spec for allowed cipher suites - can we implement?
- More HTTP/2 tests
- TLS support
- Check Tomcat defaults vs SSLLabs
- Write a Tomcat with Bouncy Castle guide
- Write a Tomcat with FFM guide
- Other
- Any open Bugzilla issue
- Expand cluster encryption to include multi-cast cluster membership
- Make non-OSGi builds more reproducible (remove Ant and JRE info from manifests)
- Better version number ordering (for parallel deployment)
- Look into adding more release automation - Airflow's Breeze is pretty interesting
- Testing
- Review test profiles and consider using JUnit
@Categoryannotation to group tests and allow them to be executed easier, then deprecate/remove thetest-profiles.propertiesfile - Log reason why tests are skipped in the
test-statusoutput - Add option to force test failure rather than skipping in cases where a dependency (like openssl) is expected to be present, but isn't. Instead of silently skipping the test should fail alerting the user that the env is missing something.
- Explore utilizing JUnit's
@Ruleannotation. Examples of usages are:- Controlling lifecycle states instead of
@Beforeor@Afterallowing you to package the behavior and use it in multiple tests without duplicating code in every test class - Using a TemporaryFolder rule could hand off the file/folder lifecycle to JUnit instead of managing it when we use File.mkdir()
- Add a TestWatcher Rule that allows you to capture and dump useful info when a test fails which could make failures much easier to diagnose
- Controlling lifecycle states instead of
- Use
Assert.assertThrows()instead of@Test(expected=...)which also allows inspecting the exception that's thrown - Explore other places to use
Assume.assumeTrue()to skip skippable env things
- Review test profiles and consider using JUnit
- Everyone's favorite topic - AI!
- How could we make tomcat more consumable by AI? Do we even want to?
- Coty (thanks for Claude) made a tomcat-docs MCP for fun a while back (based on Rich's httpd one)
- Potential for utilizing Project Magpie?
- Should we look at codifying any of our processes or tomcat project specific things into AI skills that new contributors could benefit from?