Skip to content
GitLab
Menu
Projects
Groups
Snippets
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Sign in
Toggle navigation
Menu
Open sidebar
Alexander Hirsch
703602-Compiler-Construction
Commits
415baac9
Commit
415baac9
authored
Mar 16, 2020
by
Alexander Hirsch
Browse files
Adjust information for corona situation
parent
4c1f93bf
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
35 additions
and
24 deletions
+35
-24
README.md
README.md
+10
-7
submission.md
submission.md
+25
-17
No files found.
README.md
View file @
415baac9
...
...
@@ -7,8 +7,8 @@
| 2020-03-17 | |
| 2020-03-24 | |
| 2020-03-31 | Parser complete |
| 2020-04-07 |
*no proseminar*
|
| 2020-04-14 |
*no proseminar*
|
| 2020-04-07 |
|
| 2020-04-14 |
|
| 2020-04-21 | Semantic checks complete |
| 2020-04-28 | |
| 2020-05-05 | AST → TAC conversion complete |
...
...
@@ -70,17 +70,20 @@ Both of these parts as well as the majority of QA session grades must be positiv
Be sure to adhere to the specification, deviating from it (without giving proper reason) will negatively impact your grade.
See
[
Final Submission Evaluation Scheme
](
evaluation_scheme.md
)
for more details.
###
Absence
###
Remote Seminar
You must not be absent more than three times to pass this course.
You do not have to inform me of your absence.
While university grounds are locked down, no attendance is required and no QA sessions are held.
I'll stream during the regular seminar times
[
over at Twitch
](
https://www.twitch.tv/AlexWarhawk
)
, feel free to tune in and ask questions.
Streams should be recorded by Twitch automatically and remain online for 14 days.
I recommend sending me snapshots of your code-base, I'll provide feedback while streaming.
See
[
Submission Guideline
](
submission.md
)
.
## Contacting Me
If you have questions or want to know more about a certain topic, I am always glad to help.
You can find me in room 2W05 of the ICT building.
You can
also
contact me by email, just be sure to send it from your university account.
You can contact me by email, just be sure to send it from your university account.
Please keep your email informal and include the course number in the subject.
Preferably use the following link.
...
...
submission.md
View file @
415baac9
...
...
@@ -2,19 +2,30 @@
-
Replace
`XX`
with your team number with leading zero (e.g.
`02`
).
-
One submission
*per team*
.
-
Familiarise yourself with the
`git archive`
command.
## Feedback Request
1.
Run the following command, assuming you want to submit the currently checked out version:
$ git archive --prefix=feedback_request/ --format=zip HEAD > feedback_request.zip
2.
Verify that the resulting archive contains everything you want to submit and nothing more.
3.
Ensure that the resulting archive does not contain any personal information like names or student IDs.
4.
Submit the archive via mail using the following line as subject (or link below).
703602 - Feedback Request
📧 [send email](mailto:alexander.hirsch@uibk.ac.at?subject=703602%20-%20Feedback%20Request)
## Build Test Submission
1.
`cd`
into your repository.
2.
Commit all pending changes.
3.
Checkout the revision you want to submit.
4.
Ensure the submitted code builds.
5.
Run the following command:
1.
Run the following command, assuming you want to submit the currently checked out version:
$ git archive --prefix=team_XX_build_test/ --format=zip HEAD > team_XX_build_test.zip
6
.
Verify that the resulting archive contains everything you want to submit and nothing more.
7
.
Submit the archive via mail using the following line as subject (or link below).
2
.
Verify that the resulting archive contains everything you want to submit and nothing more.
3
.
Submit the archive via mail using the following line as subject (or link below).
703602 - Team XX Build Test Submission
...
...
@@ -22,22 +33,19 @@
## Final Submission
1.
`cd`
into your repository.
2.
Commit all pending changes.
3.
Checkout the revision you want to submit.
4.
Ensure everything works.
1.
Run the following command, assuming you want to submit the currently checked out version:
$ git archive --prefix=team_XX_final/ --format=zip HEAD > team_XX_final.zip
2.
Verify that the resulting archive contains everything you want to submit and nothing more.
3.
Ensure everything works.
-
Everything builds
-
No (unjustified) warnings
-
All unit tests succeed
-
All integration tests succeed
-
No memory is leaked
-
Known issues is present and up-to-date
5.
Run the following command:
$ git archive --prefix=team_XX_final/ --format=zip HEAD > team_XX_final.zip
6.
Verify that the resulting archive contains everything you want to submit and nothing more.
7.
Submit the archive via mail using the following line as subject (or link below).
4.
Submit the archive via mail using the following line as subject (or link below).
703602 - Team XX Final Submission
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment