gemmellr commented on pull request #58: URL: https://github.com/apache/activemq-website/pull/58#issuecomment-908513677
My 'approach' for not being interested in the counts is considered with my user hat on. That whenever I am looking at a new release of anything as a user of it, I really dont have any interest at all in how many changes are in it. I care _what_ changed that impacts me, which the counts tells me next to nothing about. Releases with 1 change can be very important to me as a user, or completely irrelevant. Just like ones with 100 changes. Knowing the count doesnt help me determine that as it tells me essentially nothing by itself (except perhaps to infer whether the release is long overdue; though if it is I probably know that if I've been waiting on it). Only knowing _what_ changed gives me the detail I want as a user. Neither Kafka or Camel have such counts taking up a huge chunk of real estate on their front page that I can see. Camel has it in a linked blog post admittedly; I find it equally useless there though. I will cede the last part, caring about what is needed to update the website, is me as with my engineer hat on trying to make releases 'simple'..since they are apparently already considered enough effort that most people dont like doing (or completing) them in a timely fashion. -- 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]
