Hi team, enough time has passed since the release of 1.5.0, along with folks in the dev team we think we can start releasing Yunikorn 1.6.0. I volunteer to be the release manager.
We already have 281 items fixed in 1.6.0 according to JIRA <https://issues.apache.org/jira/issues/?filter=12352202>. We're about to release the following items/features: - Ask/Allocation unification - YUNIKORN-2457 <https://issues.apache.org/jira/browse/YUNIKORN-2457> - Preemption hardening - YUNIKORN-2493 <https://issues.apache.org/jira/browse/YUNIKORN-2493> - Establish consistent usage guidelines for Labels and Annotations - YUNIKORN-2501 <https://issues.apache.org/jira/browse/YUNIKORN-2501> - Support for OIDC credentials - YUNIKORN-2281 <https://issues.apache.org/jira/browse/YUNIKORN-2281> - Code quality: linter issues - YUNIKORN-182 <https://issues.apache.org/jira/browse/YUNIKORN-182> - Fix potential locking issues - YUNIKORN-2544 <https://issues.apache.org/jira/browse/YUNIKORN-2544> - Increased unit test coverage of different parts of the code (multiple JIRAs) - Remove StateAware scheduling - YUNIKORN-2440 <https://issues.apache.org/jira/browse/YUNIKORN-2440> - Generate reproducible binaries - YUNIKORN-2419 <https://issues.apache.org/jira/browse/YUNIKORN-2419> Well, I must say not bad!... Is there anything else worth mentioning? Things that affect backward compatibility? Anyway, the next step is to check out all items that are marked for 1.6.0 and push them out to 1.7.0. If there's any JIRA ticket that is in progress and you think it should be included in 1.6.0, please reply to this email. My plan is: * start branching on next Monday (9th Sep) * build the release artifacts * release RC1 on Wednesday and start voting (11th Sep) * end voting on Monday (16th Sep) Thoughts, opinions? Thanks, Peter
