Hi!
> Let's define a deadline. That way, rather it's ready on time and > included or not. I propose the following - Andreas has PR ready with all the tests passing by 12 March 16:00 UTC - Let's leave time for code review and fixes that have to be resolved by 16 March 16:00 UTC the latest (so two more working days) This would postpone the cut one day. I hope that's ok. If these deadlines are not met then Elasticsearch 7 support will be left out from 3.6.0 release > Speeding up release process. Thanks Benoit for explaining the bottlenecks. I think spending a day twice a year for a release is not a huge problem. But it quickly becomes a bottleneck if we want to start releasing bugfix/security update versions 3.6.1, 3.6.2 etc Let's try to come up with some ideas and agreement here: https://issues.apache.org/jira/browse/JAMES-3510 Kind regards Juhan Aasaru --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
