gemmellr edited a comment on pull request #58: URL: https://github.com/apache/activemq-website/pull/58#issuecomment-909459234
> > > Decisions?: > > 1. Single news entry per-component > > > Proposed updates: > > 1. Update the past releases pages to be dynamic and pull from the 'release data' > It already does. > 2. Update the release data to add a field to indicate release stream (ie 5.16.x, 2.18.x, etc) There is already a 'current stream' version config, and the releases are sorted so its easy to determine the latest. All thats needed is to match to the relevent component to know which versions should be compared. So perhaps the releases metadata for each component should have a 'component' field. > > 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 This is already in place. The downlaod page is already dynamic, based on the above 'current versions' config. It should handle as many streams you like: https://github.com/apache/activemq-website/blob/6d37695e9bd11cdbfbe0123e286ab7063d70d0c2/src/_data/current_releases.yml > > 4. Add follow-on task to re-work the top-banner As above this is part of this change IMO since it introduces the changes making it an issue. -- 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]
