Re: Have QA compile the help project?

[Alexia Prendergast <alexiap -at- SEAGATESOFTWARE -dot- COM>]

Hi, Lynda,

Here's what works well for us:

We develop and store our help source files in SourceSafe along with the
code. The build scripts call our makehelp.bat scripts, which build the
help--so, every time they (developers) do a new build of the software,
they get our latest changes. No muss, no fuss.

A.
--
Alexia Prendergast
Tech Pubs Manager
Seagate Software (Durham, NC, USA)
mailto:alexiap -at- seagatesoftware -dot- com

> -----Original Message-----
> I need reasons why the help author *only* should be doing the work up
> to
> the point of delivery.  OR, if anyone is handing over a
> ready-to-compile
> folder (mine's 480 files, 10MG before compiling, and one file, 780KB
> after compiling) to the QA staff, please let me know, and how well
> does
> it work?
>

Posts: mailto:techwr-l -at- listserv -dot- okstate -dot- edu
Commands: mailto:listserv -at- listserv -dot- okstate -dot- edu (e.g. SIGNOFF TECHWR-L)
Archives: http://listserv.okstate.edu/archives/techwr-l.html,
	http://www.documentation.com/, or http://www.dejanews.com/
Subjects: JOB:, QUESTION:, SUMMARY:, ANNOUNCE:, or none of these.