new entry

Lerntagebuch.md

@@ -150,4 +150,21 @@ As a result such a deduction is absurd and i petition for its removal.
 For the group project we cann apply the proper use of git. With proper use I mean keeping commits small and clean. Furthermore taking the time to create meaningful commit messages
 
 ### repetition
-Distributed scms like git allow you to work without an internet connection. Added to that your local experiments stay private and you also have implicit backups of the codebase sitting on every developer's computer. Furthermore no central server is required. But the local history getting out of sync and no protection agains concurrent changes can be disadvantageous.
+Distributed scms like git allow you to work without an internet connection. Added to that your local experiments stay private and you also have implicit backups of the codebase sitting on every developer's computer. Furthermore no central server is required. But the local history getting out of sync and no protection agains concurrent changes can be disadvantageous.
+
+## lecture 28th November 2023
+
+### takeaway
+- challenges with large software projects
+- how ci can help
+- dependency administration
+- semantic versioning
+- build process
+- continuous integration
+- collective remote repository vs. private fork
+
+### perception
+For the group project we can adhere to semantic versioning to make it clear what kind of changes are introduced with every version upgrade. Furthermore it is a good idea to make use of automated tests. This can catch bugs, increase our confidence in the code base and makes sure that introduced changes do not brake different parts of the code.
+
+### repetition
+Semantic versioning gives semantics to a version upgrade. If the first digit is incremented the new version has breaking changes. If the second digit is incremented the new version has some significant changes but is still backwards compatible. If the last digit is incremented the new version is just a patch.