nacx commented on issue #2597: Grok what exactly we are supposed to do about "official release" URL: https://github.com/apache/incubator-zipkin/issues/2597#issuecomment-492729963 So, there was a misunderstanding in the thread, regarding what we were discussing. In my feedback on the last release vote, I provided a set of items I'd like to see in both, the README and the website. * The comments on the README have been addressed. * The comments about the website still need to be done, and that's what I was referring to in the thread. Apologies if I was just asked specifically for the README bits and I answered about a different thing. This stuff is something I said I like to see _in future releases_, so I don't think everything should be fixed for the next one, since I don't know if the community is actively working on the website or it is something that will be done in future phases. For completeness, and to make it crystal clear, the README LGTM. The bits I think that need to be added to the website are: * A download page in addition to the quickstart one with links to the official Apache release (which are the source archives) as the first option. To quote an example from [LEGAL-270](https://issues.apache.org/jira/browse/LEGAL-270), _All official Apache releases are in source form; Docker images can be built from our official source releases, but are derived distributions analogous to, say, Debian packages_. So when we say official releases, we refer to the source archives the PMC votes upon. That's it. The main project website should have pointers to the official Apache source releases. Currently it only has the Quickstart guide and newcomers coming to Zipkin reading the website to learn about the project will just see the Docker image, the built jar, and a link to Github (that host the source archives for the tag, wihch is not exactly the same as the ASF source release as voted and published to the ASF repos).
---------------------------------------------------------------- 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] With regards, Apache Git Services
