Personal tools

Diagrams/Dev

From HaskellWiki

< Diagrams(Difference between revisions)
Jump to: navigation, search
(Add links to some guidelines)
(Darcs/patch-tag -> git/github migration: Ryan imported issues into github)
Line 5: Line 5:
 
What still needs to be done:
 
What still needs to be done:
   
* Import issues from [http://code.google.com/p/diagrams/issues/list Google code] into github. However, the github issue trackers are per-repo, so we'll have to import according to 'Component' tag (and the component tags may need to be cleaned up on google code first). fryguybob thinks maybe we can modify [https://github.com/arthur-debert/google-code-issues-migrator/blob/master/migrateissues.py#L100 this] to get something that will work.
 
 
* Update any and all references to patch-tag to point to github instead. This includes:
 
* Update any and all references to patch-tag to point to github instead. This includes:
 
** The diagrams website
 
** The diagrams website

Revision as of 23:06, 4 August 2012

Contents

1 Darcs/patch-tag -> git/github migration

All the diagrams repos are now migrated to github, under the diagrams organization.

What still needs to be done:

  • Update any and all references to patch-tag to point to github instead. This includes:
    • The diagrams website
    • The user manual and tutorial?
    • The packages themselves (in the .cabal files)

2 Guidelines

3 Design notes

4 Releases

5 Miscellaneous links

  • [1]: ticket re: GHC error messages with ambiguous type variables. This comes up a lot when using diagrams, it would be nice to see this ticket resolved.