mattrpav commented on pull request #58:
URL: https://github.com/apache/activemq-website/pull/58#issuecomment-908397686


   
   
   > Here's my feed-back from #57 that wasn't addressed plus a few more 
comments:
   > 
   >     1. It's not clear to me why specifically this is needed. Links to both 
Classic and Artemis releases are available just a bit further down the page, 
and NMS and CMS release links are very clearly visible on their respective 
component pages.
   
   The intent is to create a news feed. Releases, CVE, blogs, articles, 
roadmaps, etc.
   
   >     2. In terms of screen real-estate and attention, this is a pretty 
significant change to the main page. I'm not sure it makes sense for this feed 
to occupy such a prominent position. Maybe a new top-level menu item should be 
added and all these details could go there.
   
   The intent is to put the news feed front-and-center. The news feed reflects 
the community activity. There is always a ton of activity around ActiveMQ, but 
the project page is very stagnant.  
   
   >     3. 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.
   
   +100 I agree with you on this . I think the counts convey the most important 
info about the release.
   
   >     4. I don't think it's useful to have more than one release per 
component displayed. Otherwise we're advertising older releases which doesn't 
seem helpful and certainly not worth such a valuable position on the website.
   
   I think the news feed should just be natural. If there is a hot-fix release 
right after one, that should be reflected. x.y.1 releasing 1 day after x.y.0 
with 1 bug fix doesn't capture the reality that the release is changes from 
x.y.0 + x.y.1.  (Or CVE, etc)
   
   >     5. This is not so much a "news feed" as it is a "release feed."
   
   Agreed, this should be flipped back to a news feed, and pull just the top-3 
items.


-- 
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]


Reply via email to