{"push_id":630001574,"size":1,"distinct_size":1,"ref":"refs/heads/ansible","head":"adedc72d5dd6b287203f4d36461e338585a3390f","before":"ef2b2c20a6c9036d22f6bd92f288740d306ee563","commits":[{"sha":"adedc72d5dd6b287203f4d36461e338585a3390f","author":{"email":"84d4d44c69f1a0305282cdf5750cedee66efeef9@fedoraproject.org","name":"Pete Travis"},"message":"Move more branch selection to helper functions\n\nWorks with versions bound to a particular Fedora release are branched\nand built for each release.  The builders are fed a list of 'approved'\nbranches, and monitor activity in each repo for each approved branch.\n\nBranches of guides *must* follow the project-wide convention of \"fN\" for\ntheir content to be picked up.  \"F20\" doesn't count, \"f20-latest\" is\nignored, \"20\" is not published.  The builders care about \"f20\" or \"f22\".\n\nPreviously, this branch list was more or less manually maintained. This\ncommit changes that to query Fedora pkgdb instead, offloading the\nmaintenance of the list to releng, because they're doing it anyway.\n\nThere is one opportunity for docs-level policy enforcement: which\nbranches are published and which are not.  Initially, this is configured\nto publish four versions of a given work, although this is of course up\nfor discussion:\n        - The release under development (N+1, ie Alpha, Beta docs)\n        - The current primary release (N)\n        - The current maintenance release (N-1)\n        - The most recent EOL release (N-2, to help those upgrading)\n\nThere's surely a more pythonic way to grab the latest EOL release than\nmy overiterating, but I couldn't figure it out.  It works, meh.","distinct":true,"url":"https://api.github.com/repos/immanetize/anerist/commits/adedc72d5dd6b287203f4d36461e338585a3390f"}]}