Release Note problem

["Jackie Gishkin" <jgishkin -at- temposoft -dot- com>]

Hello,

I have just started a job as a technical writer in France without having
any real prior experience.  My first project is to write Release Notes
for the latest build for our "internal software".  The problem is that
the Builds are changing everyday.  Recently, I have started to write
about a new feature only to find out that it had completely changed 2
days later.  I now have to go back and delete what I wrote.  I was told
that I will be printing out the Release Notes once we come across a
really "good" Build.  

Also, instead of having a few Release Notes floating around for the same
Version, is there a way to compile them together into one coherent
document?

Since I am in a start-up, there haven't been any established ways for
doing technical documentation.

Do any of you have some advice to give me? I would apprciate it.

Thanks in advance,

Jackie Gishkin
Temposoft, FRANCE

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Develop HTML-based Help with Macromedia Dreamweaver! (STC Discount.)
**NEW DATE/LOCATION!** January 16-17, 2001, New York, NY.
http://www.weisner.com/training/dreamweaver_help.htm or 800-646-9989.

Take XML and Tech Writing courses online!  Our instructor-led courses
(4-6 hrs/wk) give you "hands on" experience at your convenience. STC members
get 20% off!  http://www.online-learning.com/index.html.
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot-  Visit
http://www.raycomm.com/techwhirl/ for more resources and info.