RE: Missing Dependencies

Hello Monti and Rosie (CC’d),

I can confirm we are using the concurrent versioning system, as required by SCEIWA. However, as discussed the origin of the project is my PLNN system (v1.0.0), thus the main branch is to be considered mine as opposed to a shared workspace.

To ensure we are all on the same page when it comes to version control for the machine learning system, please note the following for future work:

• You may copy the latest version to your branch, work there, then submit for review;
• If you wish to maintain your dependencies (i.e. artifact files) backup via floppy disk;
• I will isolate your edited version to review the value of your contributions;
• If they are usable, I will incorporate them into the main branch.

That is to say: You may not submit your work to the main branch. If you do submit to the main branch, I will revert your changes.

If you require further clarification you may discuss the matter with me directly; IT Services are not familiar with the complexities of our system and as such will not be able to assist with administration of the system in any meaningful way.

Sincerely,
Roger Isaac.

SUBJECT: Missing Dependencies

Hello Mr. Isaac,

Since we last spoke, I have been working to find the source of the dependency error in my module after copying the latest version from the main branch. It was last working in v1.0.1, but is no longer working as of v1.1.0. Through a discussion with Rosie, I’ve realised we are both experiencing similar issues on the main branch but not our own workspaces.

Should we be using the concurrent versioning system, or is there a different process in place?

Any insight you can provide would be appreciated. After this, my next step towards identifying the source of the problem will be to contact IT Services.

Regards,
Monti Amaal.