> Am 17.05.2018 um 15:13 schrieb Eric Covener <[email protected]>: > > I tried to collect some bullets here: > https://wiki.apache.org/httpd/ReleaseStrategyProposal > > If anyone else has priorities/problems/proposals/refinements please have a > look.
Thanks for putting in the effort. With the mail storm some days ago, I did not get a feeling that we have some sort of common ground on how to go forward. The opinions seem to vary quite a bit, to put it conservatively. From my personal point of view (which is mine, but not necessarily the correct one for the project), bringing in new functions like http2 or Let's Encrypt requires a lot of patience. And, due to the lousy test coverage, you can never be sure not to have destroyed someone's previous use case. So, any boldness - without which there would be no progress - gets easily penalized (see the mod_md vs. mod_ssl breakage). I am amazed, not surprised, but still have this sense of awe and wonder when I see how many show up when it comes to discussing processes and restrictions for the few people who actually do still write code or documentation. This I find funny - in my good moments. Anyways, I am in maintenance mode these days. What could motivate me again for trying new things - just to make clear where I stand - is: - monthly, non-2.4 releases with CTR policy, with API breakage more likely than not each month. Preferably starting with a 2.4.x copy, ditching trunk. - join 2-3 people who *do* a restart of our test cases. I would contribute adapted mod_http2 and mod_md test suites into that. My €0.02. Cheers, Stefan
