79764df2d5
The process was too fragile. It made too many assumptions about available libraries (which failed sometimes when sandboxes were used). This is a low-tech solution. The only drawback is that `man/pandoc.1` is a generated file in the repository. It will need to be regenerated periodically when README changes.
31 lines
602 B
Text
31 lines
602 B
Text
_ Test, on linux, windows, mac (inc. website demos)
|
|
|
|
_ Finalize changelog
|
|
|
|
_ man man/pandoc.1 and commit if needed
|
|
|
|
_ Tag release in git
|
|
|
|
_ Tag templates
|
|
|
|
_ 'make dist' to generate tarball
|
|
|
|
_ Generate Windows package and copy to directory.
|
|
|
|
_ Generate Mac OSX package.
|
|
|
|
_ Generate Ubuntu/Debian deb package.
|
|
|
|
- Add release on github (and upload files)
|
|
|
|
_ Upload to HackageDB
|
|
|
|
_ Update website, including short description of changes
|
|
|
|
_ Announce on pandoc-announce, pandoc-discuss
|
|
|
|
_ on server, 'cabal install --enable-tests -ftrypandoc'
|
|
and then 'cd trypandoc; sudo make install'
|
|
|
|
_ recompile gitit
|
|
|