[fusion-dev] Re: Commit Process for Fusion

[Paul Spencer]

No particular process but for larger commits that potentially break  
lots of stuff, it would be good to post a patch (use svn diff) for  
review.

You should be creating/using tickets for all commits but for trivial  
ones like whitespace and documentation updates we don't bother  
normally.  Sometimes a commit slips through without a ticket though,  
that's usually okay but if it is an important improvement its good to  
record it somewhere where it can be noted in the release notes.

Cheers

Paul

On 2009-11-10, at 8:47 AM, Nolte, Tim wrote:

> Hey Paul,
>
> Again just trying to make sure I'm following the correct protocols  
> here.
> I'm ready to commit some changes to the trunk. Is there a code
> review/approval process that I need to follow? Also, for any changes
> that I make should I be creating a Trac ticket if there isn't one
> already, so that I can tag my commit with a ticket #? Thanks!
>
> - Tim
>
> ----
> Timothy J Nolte - tnolte at ilpcs.com
> Network Planning Engineer
>
> iPCS Wireless, Inc.
> 4717 Broadmoor Ave, Suite G
> Kentwood, MI 49512
>
> Office: 616-656-5163
> PCS:    616-706-2438
> Fax:    616-554-6484
> Web: www.ipcswirelessinc.com


__________________________________________

    Paul Spencer
    Chief Technology Officer
    DM Solutions Group Inc
    http://research.dmsolutions.ca/