Nginx.org: Please differentiate stable and dev versions on download.html
|Reported by:||Simon B||Owned by:|
This issue is reported regarding the web-site www.nginx.org (in particular the http://www.nginx.org/en/download.html page and the http://www.nginx.org/download/ directory). It's not related in any way to a particular version of nginx, so please dis-regard those entries which were required to contain valid values in order to submit this form.
For those of us who use scripts to determine whether we need to update (or in my case, I'm working on an automated build system for servers based on LFS); please add some way to automatically differentiate stable and release versions on your downloads page.
This could be achieved in any one of a number of ways, such as:
a) putting -dev in the file names of development releases (which would also help if viewing the http://www.nginx.org/download/ folder directly); or
b) by putting them in a different directory (/download/dev vs /download/releases); or
c) on a different web-page (so download.html which can link to download-dev.html for development versions); or
d) by having some parameter one could pass to the web-page to view only releases (such as download.html?releases); or
e) by sym-linking the current release version such that it's obtainable either by looking at the content-disposition of the served page; or
f) by having a page that does a 30x redirect to the correct file; or
g) by having a numbering convention, such as "the second number being odd denotes test version - so 1.2.3 is release and 2.3.4 is test". By looking at your downloads folder I could not ascertain any such system, but if one exists please note it on download.html.
(Hopefully one is very simple? I can't be the only person who wants to do this :-).
Right now a script would have to parse HTML to determine which are release versions; which is difficult at best -- and a bit harder in this case as the download is in the middle of a massive unformatted block.