mattrpav edited a comment on pull request #58: URL: https://github.com/apache/activemq-website/pull/58#issuecomment-908399541
> @jbertram > > > 1. The summary information (i.e. bugs, enhancements, dependencies) is no longer present. I thought this info was useful as it succinctly communicated the character of the release. > > I think that was probably removed after I said on the other PR that I didnt see it is as being all that useful, especially for a feed area I dont think it remotely warrants the space burned on it. Even whats left is still too big IMO. > > I dont think it truly helps you usefully characterise the release most of the time personally. Without seeing an overview of what the changes are you cant really tell much of anything about their importance or relevance from the number of them. The number itself is also often just a consequence of how long it is since the last release was done, rather than anything inherent about the actual changes themselves (e.g Artemis 2.18.0 took 6 months, but many of those changes could/should have gone out months earlier with followup releases later for more changes, they just didnt. More than ditto for 5.17.x when it happens). > > Plus the 'number of bugs/etc' summary complicates the steps needed to add a release to the site. People already seem to find that too much of a chore to do as it is so I would skip it for that alone. I agree w/ @jbertram and contend @gemmellr's approach is an "engineer" perspective vs an end-user that manages a handful of ActiveMQ clusters along with 5 or 6 other products. We should target the end-user audience with the community front-page. Kafka and Camel are doing really well with this approach. -- 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]
