Difference between revisions of "Yi/PreparingARelease"

From HaskellWiki
< Yi
Jump to: navigation, search
Line 7: Line 7:
 
# Prepare a source tarball
 
# Prepare a source tarball
 
# Prepare haddocked API html
 
# Prepare haddocked API html
# Test it; in particular, make sure Yi can be installed on a fresh box without undue hassle.
+
# Test it; in particular, make sure Yi can be cabal-installed easily.
 
# Have yi-devel people test it (as above)
 
# Have yi-devel people test it (as above)
# When ok, tag the version with release number.
+
# When ok, tag the version with release number and make corresponding tarball.
 
# Prepare release notes
 
# Prepare release notes
#* release notes should be hosted on a server that can stand a bit of load; last time haskell.org was taken down because the Yi wiki page was posted on Reddit. There should at least be some buffer between what will endup in news and the wiki page.
+
#* release notes should be hosted on a server that can stand a bit of load; 0.2 release took down haskell.org because the Yi wiki page was posted on Reddit. There should at least be some buffer between what will endup in news and the wiki page.
 
#* screenshots are nice, think of including one.
 
#* screenshots are nice, think of including one.
 
# Upload tarball on Hackage
 
# Upload tarball on Hackage
Line 18: Line 18:
 
* http://www.haskell.org/pipermail/haskell/2005-March/015615.html
 
* http://www.haskell.org/pipermail/haskell/2005-March/015615.html
 
* http://www.haskell.org/pipermail/haskell/2007-May/019498.html
 
* http://www.haskell.org/pipermail/haskell/2007-May/019498.html
  +
* http://www.haskell.org/pipermail/haskell/2008-January/020166.html

Revision as of 14:53, 27 July 2008

Preparing a release for Yi is not as trivial as it seems: there are quite a few people interested, and screwing up is therefore not good :)

I advise the following steps:

  1. Make sure the quality is acceptable
  2. Update the contributors list
  3. Prepare a source tarball
  4. Prepare haddocked API html
  5. Test it; in particular, make sure Yi can be cabal-installed easily.
  6. Have yi-devel people test it (as above)
  7. When ok, tag the version with release number and make corresponding tarball.
  8. Prepare release notes
    • release notes should be hosted on a server that can stand a bit of load; 0.2 release took down haskell.org because the Yi wiki page was posted on Reddit. There should at least be some buffer between what will endup in news and the wiki page.
    • screenshots are nice, think of including one.
  9. Upload tarball on Hackage
  10. Upload doc (Hackage too?)
  11. post announce on haskell.org. Previous releases: