Blip

Planning: Track project releases

We'd like to track the releases for a given module in Blip. Thoughts:

• We can probably just scan a given HTTP location for releases. We can and should use an install-module hook or email hook to trigger a scan, but we can't rely on these as the only source of information. We always like to get historical information from before we ever got triggers.
• We should figure out how to extract the NEWS entry for a single release.
• Releases should probably be associated with a branchable. Then a branch shows release for its branchable which have a version number matching the unstable or stable version stored for that branch.
• It would be nice to have a record of vendor packages of releases. Can we get a synopsis of vendor patches on vendor packages?