> > I saw that we already have a JIRA filter for 1.0 > <https://issues.apache.org/jira/projects/YUNIKORN/versions/12350288>. >
The release and version information is only available if and when you are authenticated to jira. That excludes people. For unauthenticated access it is better to use searches like the ones already available: Current release target: https://issues.apache.org/jira/issues/?filter=12348416 Fixed in 1.0.0: https://issues.apache.org/jira/issues/?filter=12350818 These links we can also include in a release preparation page on the website. It does come back to properly using the "target version" and "fixed in version" fields. Using the fixed in version field for release planning causes issues as it requires bulk updates for issues that miss a release. If the issue slips the release it has to be updated otherwise the release note shows issues as included while they are still open. Using two fields allows us to target a fix for an issue in a release without impacting the release notes. It will become more important when we start creating maintenance releases on top of older releases with backports. Wilfred
