Pdns: consider reordering repo.powerdns.com to favor newer stuff

Created on 25 Jul 2017  Â·  6Comments  Â·  Source: PowerDNS/pdns


  • Program: Authoritative, Recursor, dnsdist
  • Issue type: Feature request

Short description


The order of linux distributions (especially Debian and Ubuntu) is really not ideal. It favors old things for no particular reason.

Environment

Web Browser

Steps to reproduce

I was looking for the repo info for Debian 9 Stretch (but half the time i'm looking for an Ubuntu or a different Debian, or potentially a RHEL).

  1. visit https://repo.powerdns.com/
  2. Click Debian
  3. See "powerdns authoritative server version 4.0.x" and expand it

Expected behaviour

There are a number of ways to improve this:

  • [x] Don't auto expand the second level (distro releases) when someone expands the first level (distro brands)
  • [x] Change the order to favor newer releases over older releases
  • [ ] Possibly split LTS out of the normal flow (they're in a lot of ways a distinct product from normal releases -- with a distinct customer base -- consider RHEL vs. Fedora -- they're very related, but practically unrelated customers -- same for CentOS, very related, but distinct customers)
  • [ ] Switch to a series of [ |v] drop downs instead of a tree, an example of that is used by the PPA system, as in launchpad vim:

    1. click "Technical details about this PPA"

    2. select an item in: Display sources.list entries for:

Actual behaviour

Tree auto expanded to show Debian 8 children which obscured the presence of Debian 9.

Note that it's much worse for Ubuntu, the first entry expanded is 14.04 (the older LTS), the second is 16.04 (the latest LTS), the third is 16.10 (obsolete), the last is 17.04 (the current release).

Note: the behavior is also not very helpful at the next tier:
If a user is looking for something, they probably only care about a single product (auth, dnsdist, recursor, metronome) -- showing them all of the various versions of all the products they don't want isn't helpful.

w/ a dropdown, I'd probably preselect the latest release branch but have "master" above and all the older things below.

Other information

Usecase

Make it easy for customers to pick the right product.

Description

feature request repo

Most helpful comment

Note: the site is now sorted by latest first.

This is no longer true (at least for Ubuntu), reopening. Thanks @vandalon

All 6 comments

I like the idea and you're right that right now the site is a little messy, I'll have to poke an HTML / CSS guru to create a nice template for me to fill in through ansible though :)

Note: the site is now sorted by latest first.

@jsoref can this be closed?

@Habbie: I'd say yes, the first two items have been done.

I'd note that there's one section on this page that's out of order:

For dnsdist, there are also different repositories:

  • master — GitHub master branch. Useful for testing, expect breakage.
  • 10 — 1.0.X releases.
  • 11 — 1.1.X releases.
  • 12 — 1.2.X releases.

I'm pretty sure it should be:

  • master
  • 12
  • 11
  • 10

@jsoref Those are sorted now as well!

Note: the site is now sorted by latest first.

This is no longer true (at least for Ubuntu), reopening. Thanks @vandalon

Was this page helpful?
0 / 5 - 0 ratings