michaeljmarshall commented on pull request #10829:
URL: https://github.com/apache/pulsar/pull/10829#issuecomment-857200858


   > @michaeljmarshall just my two cents: seems that the contents of Supported 
Versions in this PR are not appropriate to be located in the Pulsar Security 
Chapter (which should include secure the components in your Pulsar deployment, 
configure encryption/authentication/authorization, and more).
   
   I don't have strong feelings about its location and am happy to move it to 
another location. I was thinking it could belong in the Security chapter 
because security vulnerabilities only really affect users that are actually 
using the security features, and the only way to know that you are not subject 
to known security vulnerabilities is to run on the latest supported version for 
a given minor release.
   
   In looking at your screen shots from the Apache Spark website, they have 
similar information here: https://spark.apache.org/versioning-policy.html. That 
`Developers` tab seems appropriate, but I'm not seeing the same type of 
tab/chapter on the pulsar site. I like that the Apache Spark one is not 
versioned. Do you we have sections of docs that are not versioned?
   
   Also, I can see that they have a reference to the Apache security link in a 
location similar to our current set up:
   
   <img width="1255" alt="Screen Shot 2021-06-08 at 3 40 16 PM" 
src="https://user-images.githubusercontent.com/47911938/121262954-29520480-c872-11eb-9759-ec1e135f28d2.png";>
   
   @Anonymitaet - are you open to adding a new tab in the top banner named 
"Developers"? That could be a natural location for the supported version 
information as well as the listing our known security vulnerabilities. It could 
be very similar to the Apache Spark implementation.
   
   


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

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to