30 Jan
2014
30 Jan
'14
11:53 a.m.
Clark Gaebel
How does the process of taking over maintenance add latency to your work?
1) Check out broken version of package. 2) Fix locally, bump version number locally. 3) cabal sandbox add-source ../fixed-package in any package that needs the fixed version. 4) Email hackage admins for upload rights. 5) Continue working on your actual project. 6) Receive upload privileges one day. 7) Upload fixed package.
As far as I can tell, the only real latency cost here is that paid to fix the broken version.
In my experience, step 4 involved several round trips between a number of different people. Admittedly, this is in part because it's easy to forget about the broken package after you have fixed it locally. Cheers, - Ben