Re: [Audacity-manual] Tracking changes across pages

[Gale A. <ga...@au...>]

| From Peter Sampson <pet...@ya...> 
| Sat, 25 Feb 2012 09:56:46 -0800 (PST)
| Subject: [Audacity-manual] Tracking changes across pages
> Gale wrote:
> >You are all agreeing with Ed, but not suggesting a lot to prevent Manual
> >bugs being missed again.
> 
> Well I agree with Ed too.
>  
> having someone on Q/A trawl through the technical details of commit logs is a 
> back-to-front way of doing things and far from efficient  - and it would still be far 
> too easy to miss changes.
>  
> Any developer *knows* when they have made a modification to the existing GUI 
> (added/removed a check box, re-arranged a dialog box, added a menu item or whatever)
>  or added completely new functionality.  I believe that as a fundamental part of the dev 
> commit process the developer should be informing the manual team, via this email list, 
> of GUI changes that have been committed when they are committted.  This is not an 
> onerous additional task and I think it is quite reasonable to ask the developers to do this 
> as part of their commit process. 

I for one would not welcome extra e-mails given I already subscribe to 
SVN commits. Just let the developers consider the content of the commit 
logs (as I said at the outset) and let the person who agrees to take charge 
of tracking changes on the Manual make sure he subscribes to commits. 

Developers are humans like everyone and may omit to note something 
relevant to the Manual in the log. I think if the process is to e-mail 
changes to this list, they will be much more likely to forget. So someone 
looking inside the commits is a good backup. 

If we don't have a due process for tracking changes, then we can hardly
bang the drum about the devs not noting Manual changes in commits. 
So can we agree a process at our end? 

At a minimum, I think the lead Manual person (Bill) and lead Forum 
person (Steve) should be subscribed to SVN commits. I thought Steve 
was? 
   



Gale