It's UWAweek 50

help2002

This forum is provided to promote discussion amongst students enrolled in CITS2002 Systems Programming.
Please consider offering answers and suggestions to help other students! And if you fix a problem by following a suggestion here, it would be great if other interested students could see a short "Great, fixed it!"  followup message.
Displaying the 2 articles in this topic
Showing 2 of 835 articles.
Currently 5 other people reading this forum.


 UWA week 35 (2nd semester, week 6) ↓
SVG not supported

Login to reply

👍?
helpful

Do not know it is a proper way to let everyone know content changes of the project description. Update timestamps let everyone know whether the content has changed or not since the last time they checked out (if they still remember the date). Change logs are brief messages of changes that everyone should focus on, meaning that they just need to read corresponding sections, instead of reading the whole description and examining differences. Any good ideas? Thanks a lot.


SVG not supported

Login to reply

👍x1
helpful

"Junyu Zhang" <24*6*1*2@s*u*e*t*u*a*e*u*a*> wrote:
> Do not know it is a proper way to let everyone know content changes of the project description. > Update timestamps let everyone know whether the content has changed or not since the last time they checked out (if they still remember the date). > Change logs are brief messages of changes that everyone should focus on, meaning that they just need to read corresponding sections, instead of reading the whole description and examining differences.
Not quite sure of the context of this post. The intention is to *not* make any changes to the project description once it is finalised (as it was very early this morning, and announced in an announcement on this forum). Any necessary changes from now will be announced on the project's Clarifications page, each with the date/time of any change.

The University of Western Australia

Computer Science and Software Engineering

CRICOS Code: 00126G
Written by [email protected]
Powered by history
Feedback always welcome - it makes our software better!
Last modified  8:08AM Aug 25 2024
Privacy policy