rel-html: fix stable release attribute search

Each release has a set of things we need to verify
prior to publishing a URL for it. For example a stable
release requires:

  * ChangeLog
  * Signed ChangeLog
  * Tarball
  * Signed tarball

We search for these files based on a pivot 'release'
version string. The existing algorithm was using the
full release version but given that for example
compat-drivers relies on only one ChangeLog for
the different modified release types the search was
skipping out on finding a ChangeLog for modified
stable releases.

So for example compat-drivers-3.8.2-2-su relase uses
the ChangeLog-3.8.2-2, but as it was before this commit
the search was looking for "3.8.2-2-su" in the URL
attributes it was looking, not 3.8.2. This change
modifies parsing the URLs it looks at by looking at
the short version instead.

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>
1 file changed
tree: b7eaec56ac617971a1e051b7bc623b5001255385
  1. html/
  2. projects/
  3. agpl-3.0.txt
  4. CONTRIBUTING
  5. LICENSE
  6. README.md
  7. rel-html.cfg
  8. rel-html.py
README.md

rel-html

rel-html is designed to parse naked index html pages with tarballs on a software project and automatically produce a nice shiny HTML5 release page for you. It takes as input a configuration file, rel-html.cfg, in which you can specify attributes for the release.

Example release page

TODO

  • Figure out how to automatically determine releases from git.

    • If we have many stable releases how should we annotate this via git ?
  • See if we can copy the EOL release into an eol/ directory and moving forward instead of parsing the tags use the directory name to automatically determine other release attributes.