gemmellr commented on issue #17: Fix the ordering in the security advisories page URL: https://github.com/apache/activemq-website/pull/17#issuecomment-544923933 I think either way can be confusing in one way or the other in the face of such disparity of actual-vs-reference dates. E.g, having moved that 2015 referenced issue into the 2015 group, folks might now reasonably think it was resolved in a 2016 release (say, one which they might have started using to fix one of the listed 2016 issues), which it was not since it was only addressed in 2017 (and thus originally in the 2017 group). Avoiding groupings entirely seems like it might be better... e.g strict order of release, or clearly noted affected+fix versions directly on the page (rather than on click-through to the advisory text itself), or even both.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
