Changes between Version 3 and Version 4 of WorkingConventions/AddingFeatures


Ignore:
Timestamp:
Jan 29, 2013 3:00:07 PM (15 months ago)
Author:
henrique
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WorkingConventions/AddingFeatures

    v3 v4  
    66 0. '''Take ownership of the ticket in Trac''', by using the "Action" chunk at the bottom of the Trac bug display (you need to be logged in to see it), and putting your name in the "reassign to" box.  This makes sure that two people don't work on the same feature.  If you later decide you can't do it after all, remove your name.[[BR]][[BR]] 
    77 0. '''Write down the specification of the feature''' and either add it directly to Trac, or put it on a web page somewhere else and link to it.  Specifying before implementing is obviously a good idea; and it makes it possible for others to comment on your design before you invest heavily in building the feature.[[BR]][[BR]] 
    8  0.  '''Get feedback''' by emailing a suitable list (`cvs-ghc` for nitty-gritty GHC internals, `glasgow-haskell-users` for user-visible features).  Often you'll get useful ideas.[[BR]][[BR]] 
     8 0.  '''Get feedback''' by emailing a suitable list (`ghc-devs` for nitty-gritty GHC internals, `glasgow-haskell-users` for user-visible features).  Often you'll get useful ideas.[[BR]][[BR]] 
    99 0. '''Implement the feature'''! 
    1010   * Please follow our [wiki:WorkingConventions#Coding coding conventions]