All our packages have a
*.changes file and ideally that file would mention relevant changes from upstream, i.e. during version updates. Currently, we find that information manually when packaging Haskell software. This is unsatisfactory because of the sheer size of the package set and the massive number of updates we receive from Hackage. The packaging itself is completely automatic, but editing the
*.changes files is not and this issue prevents us from shipping more packages in Tumbleweed and elsewhere.
Now, during this Hackweek I'd like to write code that given two Haskell package versions
new can determine the upstream changelog entries between those two and create a pleasantly formatted entry for the
*.changes file that won't need any manual editing to pass the review team. Then I'd like to integrate this into
cabal2obs, or maybe even
Looking for mad skills in:
This project is part of:
Hack Week 17
Theoretically, Haskell should be perfect for im...