powerdns repository idea

gistfile1.txt

We often get requests for a PowerDNS package repository to ease updating. This is our idea on how we'll implement this.

There will be a repository that always gives you 
  1) auth and recursor from the tip of master or other branches ("scary-master", "scary-oneshot")
  2) auth and recursor from 3.3.x, where we promise that updates within 3.3.x will never break ("auth-3.3, recursor-3.5")
  3) auth and recursor "highest released version" ("auth-release", "recursor-release")

So to upgrade to a newer version, either:
  1) just update and get whatever pain we want to inflict on you
  2) update and get something that Should Just Work
  3) update and get a properly released version that might barf on your configuration or schema

Note that this policy also implies a new promise for minor releases: no breaking.