Hi Shaun,
Do you mean that NOTIFIED and PUBLISHED can also work in the
reverse
order? Can you please take that again? I'm interested in
hearing about
how you'd like to use the different codes.
Per
>> I guess that NOTIFIED is implied when setting the
status PUBLISHED, as
>> communicating to the users is something you never
forget as a NLC
>> project.
>>
>> But I guess that it wouldn't harm to have it in the
list. If you have
>> the time to publish the build day 3 you might not
have the time to work
>> with an announcement the next day, therefore
wanting to be reminded the
>> next time you log into QATrack that the
notification is still not done.
>>
>> It's not a bad idea, the system can let each user
use the statuses
>> differently, or just skip PUBLISHED and set
NOTIFIED directly.
>>
>> Anyone like to add a thought to this? If there are
no organizational
>> problems that might occur, I'll implement this
feature.
>>
>
> This is an excellent explanation of the status usage. I
need to add some
> builds to some places like versiontracker, thus the
notified state. I
> will often make the builds available on the pages first
before the
> notification goes out.
>
> Shaun
> [...]
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe qa.openoffice.org
For additional commands, e-mail: dev-helpqa.openoffice.org
|