lucastetreault commented on pull request #58: URL: https://github.com/apache/activemq-website/pull/58#issuecomment-909459047
> Decisions?: > > 1. Single news entry per-component I don't have a strong opinion either way on this one... I think there's value in showing sequential releases... E.g.: a 2.18.0 release and 2.18.1 release 2 days later is interesting context for users. I understand the worry about driving users to versions we don't want them using though. > Proposed updates: > > 1. Update the past releases pages to be dynamic and pull from the 'release data' > 2. Update the release data to add a field to indicate release stream (ie 5.16.x, 2.18.x, etc) > 3. Update the download page to show most recent release for 'active' streams. This would just be a hard-coded values (ie 5.16.x, 5.17.x and 2.18.x, etc) in the page to keep the complexity low > 4. Add follow-on task to re-work the top-banner 1-3 are all already done! -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
