Closed clintropolis closed 5 years ago
@clintropolis did the older releases get moved to the bottom of the page?
@clintropolis did the older releases get moved to the bottom of the page?
Yeah, I moved them to the bottom to downplay the older releases. The are going to be served from the archives per apache policy that only latest releases be on the mirrors, which doesn't support the /dyn/closer.cgi?path=
stuff that the mirrors do which I think plays into how downloads are tracked.
I would prefer this not merged until we understand impacts of all changes in webpage
I would prefer this not merged until we understand impacts of all changes in webpage
Anything I can do to help? This is the last thing I have to do before I can officially announce the release.
Which part are you worried about, moving the older releases to the bottom of the page or the older releases being served from the archive?
Not sure there is much I can do about the latter, but download pages for other Apache projects are similar where only actively developed branches are served from the mirrors. Taking Apache Kafka for example, the latest 2.2.x and 2.1.x releases are from the mirrors, the rest are from the archives. Apache Spark only has the latest release available from the mirrors on their download page, and a single link to the archives for all older releases. Apache Hadoop has several active release lines so has all of those from the mirrors on the download page, and like Spark a link to the archives for any release not on the page.
We would be ok with 0.14.2-incubating and 0.13.0-incubating being on the mirrors since they are the latest of 0.14.x and 0.13.x, and 0.14.1 and 0.14.0 in the archives, but since we aren't actively developing for 0.13.0-incubating I thought it made more sense for it to live chronologically in the 'Older releases' section instead.
I would prefer this not merged until we understand impacts of all changes in webpage
@fjy could you elaborate on what potential impacts you think we should investigate?
@clintropolis @fjy how do you feel about keeping the set of releases on the mirrors and on downloads.html matching (ie avoid archive links)? Post 0.14.2 release it should probably be either just 0.14.2, or 0.14.2 plus 0.13.0. (i.e. latest patch release from the last two major lines)
@clintropolis @fjy how do you feel about keeping the set of releases on the mirrors and on downloads.html matching (ie avoid archive links)? Post 0.14.2 release it should probably be either just 0.14.2, or 0.14.2 plus 0.13.0. (i.e. latest patch release from the last two major lines)
That sounds fine to me, I don't have very strong opinions on this. I think in that case I would put both 0.14.2 and 0.13.0 in the top again like the current layout of the page, and then at the bottom instead of enumerating all the archive releases, change the heading to 'Release archive' and link to https://archive.apache.org/dist/incubator/druid/
Likewise, probably the same should be done in apache site here https://github.com/apache/incubator-druid-website/pull/6 if we go with this approach, with 0.14.2 an 0.13.0 in the table and a link below to the archives
I have updated the PR description based on discussion so far
👍 if we're certain it won't negatively impact webpage
Adds download link for 0.14.2-incubating, slightly reworks download page to serve only latest releases from the latest 2 release branches the mirrors, and adds a link to
archive.apache.org
at the bottom of the downloads page in a 'Older releases' section....
in
_config.yml
the versions property has been modified to group versions by release:which the downloads page takes the first version of the first 2 groups to link to mirrors. News sidebar is essentially unchanged.