DOCSLIB.ORG

Distributed Version Control Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Distributed Version Control Systems Prehistory History Linux Bazaar Conclusion Distributed Version Control Systems Matthieu Moy Computer Science and Automation Indian Institute of Science Bangalore October 2006 Matthieu Moy (CSA/IISc) DVC October 2006 < 1 / 43 > Prehistory History Linux Bazaar Conclusion Outline 1 Motivations, Prehistory 2 History and Categories of Version Control Systems 3 Version Control for the Linux Kernel 4 Bazaar (bzr): One Decentralized Revision Control System 5 Conclusion Matthieu Moy (CSA/IISc) DVC October 2006 < 2 / 43 > Prehistory History Linux Bazaar Conclusion Outline 1 Motivations, Prehistory 2 History and Categories of Version Control Systems 3 Version Control for the Linux Kernel 4 Bazaar (bzr): One Decentralized Revision Control System 5 Conclusion Matthieu Moy (CSA/IISc) DVC October 2006 < 3 / 43 > I Replicate: $ cp -r ~/project/ ~/backup/ I Keep history: $ cp -r ~/project/ ~/backup/project-2006-10-4 I Keep a description of history: $ echo "Description of current state" > \ ~/backup/project-2006-10-4/README.txt Historical solutions: Prehistory History Linux Bazaar Conclusion Backups: The Old Good Time Basic problems: I “Oh, my disk crashed.” / “Someone has stolen my laptop!” I “@#%!!, I’ve just deleted this important file!” I “Oops, I introduced a bug a long time ago in my code, how can I see how it was before?” Matthieu Moy (CSA/IISc) DVC October 2006 < 4 / 43 > I Replicate: $ cp -r ~/project/ ~/backup/ I Keep history: $ cp -r ~/project/ ~/backup/project-2006-10-4 I Keep a description of history: $ echo "Description of current state" > \ ~/backup/project-2006-10-4/README.txt Prehistory History Linux Bazaar Conclusion Backups: The Old Good Time Basic problems: I “Oh, my disk crashed.” / “Someone has stolen my laptop!” I “@#%!!, I’ve just deleted this important file!” I “Oops, I introduced a bug a long time ago in my code, how can I see how it was before?” Historical solutions: Matthieu Moy (CSA/IISc) DVC October 2006 < 4 / 43 > I Keep history: $ cp -r ~/project/ ~/backup/project-2006-10-4 I Keep a description of history: $ echo "Description of current state" > \ ~/backup/project-2006-10-4/README.txt Prehistory History Linux Bazaar Conclusion Backups: The Old Good Time Basic problems: I “Oh, my disk crashed.” / “Someone has stolen my laptop!” I “@#%!!, I’ve just deleted this important file!” I “Oops, I introduced a bug a long time ago in my code, how can I see how it was before?” Historical solutions: I Replicate: $ cp -r ~/project/ ~/backup/ Matthieu Moy (CSA/IISc) DVC October 2006 < 4 / 43 > I Keep a description of history: $ echo "Description of current state" > \ ~/backup/project-2006-10-4/README.txt Prehistory History Linux Bazaar Conclusion Backups: The Old Good Time Basic problems: I “Oh, my disk crashed.” / “Someone has stolen my laptop!” I “@#%!!, I’ve just deleted this important file!” I “Oops, I introduced a bug a long time ago in my code, how can I see how it was before?” Historical solutions: I Replicate: $ cp -r ~/project/ ~/backup/ I Keep history: $ cp -r ~/project/ ~/backup/project-2006-10-4 Matthieu Moy (CSA/IISc) DVC October 2006 < 4 / 43 > Prehistory History Linux Bazaar Conclusion Backups: The Old Good Time Basic problems: I “Oh, my disk crashed.” / “Someone has stolen my laptop!” I “@#%!!, I’ve just deleted this important file!” I “Oops, I introduced a bug a long time ago in my code, how can I see how it was before?” Historical solutions: I Replicate: $ cp -r ~/project/ ~/backup/ I Keep history: $ cp -r ~/project/ ~/backup/project-2006-10-4 I Keep a description of history: $ echo "Description of current state" > \ ~/backup/project-2006-10-4/README.txt Matthieu Moy (CSA/IISc) DVC October 2006 < 4 / 43 > Prehistory History Linux Bazaar Conclusion Backups: Improved Solutions Replicate over multiple machines Incremental backups: Store only the changes compared to previous revision I With file granularity I With finer-grained (diff) Many tools available: I Standalone tools: rsync, rdiff-backup,... I Versionned filesystems: VMS, Windows 2003+, cvsfs, . Matthieu Moy (CSA/IISc) DVC October 2006 < 5 / 43 > I Never two person work at the same time. When one person stops working, (s)he sends his/her work to the others. ⇒ Doesn’t scale up! Unsafe. I People work on the same directory (same machine, NFS, . ) ⇒ Painful because of (2) above. I People lock the file when working on it. ⇒ Doesn’t scale up! I People work trying to avoid conflicts, and merge later. Historical solutions: Prehistory History Linux Bazaar Conclusion Collaborative Development: The Old Good Time Basic problems: Several persons working on the same set of files 1 “Hey, you’ve modified the same file as me, how do we merge?”, 2 “Your modifications are broken, your code doesn’t even compile. Fix your changes before sending it to me!”, 3 “Your bug fix here seems interesting, but I don’t want your other changes”. Matthieu Moy (CSA/IISc) DVC October 2006 < 6 / 43 > I Never two person work at the same time. When one person stops working, (s)he sends his/her work to the others. ⇒ Doesn’t scale up! Unsafe. I People work on the same directory (same machine, NFS, . ) ⇒ Painful because of (2) above. I People lock the file when working on it. ⇒ Doesn’t scale up! I People work trying to avoid conflicts, and merge later. Prehistory History Linux Bazaar Conclusion Collaborative Development: The Old Good Time Basic problems: Several persons working on the same set of files 1 “Hey, you’ve modified the same file as me, how do we merge?”, 2 “Your modifications are broken, your code doesn’t even compile. Fix your changes before sending it to me!”, 3 “Your bug fix here seems interesting, but I don’t want your other changes”. Historical solutions: Matthieu Moy (CSA/IISc) DVC October 2006 < 6 / 43 > I People work on the same directory (same machine, NFS, . ) ⇒ Painful because of (2) above. I People lock the file when working on it. ⇒ Doesn’t scale up! I People work trying to avoid conflicts, and merge later. Prehistory History Linux Bazaar Conclusion Collaborative Development: The Old Good Time Basic problems: Several persons working on the same set of files 1 “Hey, you’ve modified the same file as me, how do we merge?”, 2 “Your modifications are broken, your code doesn’t even compile. Fix your changes before sending it to me!”, 3 “Your bug fix here seems interesting, but I don’t want your other changes”. Historical solutions: I Never two person work at the same time. When one person stops working, (s)he sends his/her work to the others. ⇒ Doesn’t scale up! Unsafe. Matthieu Moy (CSA/IISc) DVC October 2006 < 6 / 43 > I People lock the file when working on it. ⇒ Doesn’t scale up! I People work trying to avoid conflicts, and merge later. Prehistory History Linux Bazaar Conclusion Collaborative Development: The Old Good Time Basic problems: Several persons working on the same set of files 1 “Hey, you’ve modified the same file as me, how do we merge?”, 2 “Your modifications are broken, your code doesn’t even compile. Fix your changes before sending it to me!”, 3 “Your bug fix here seems interesting, but I don’t want your other changes”. Historical solutions: I Never two person work at the same time. When one person stops working, (s)he sends his/her work to the others. ⇒ Doesn’t scale up! Unsafe. I People work on the same directory (same machine, NFS, . ) ⇒ Painful because of (2) above. Matthieu Moy (CSA/IISc) DVC October 2006 < 6 / 43 > I People work trying to avoid conflicts, and merge later. Prehistory History Linux Bazaar Conclusion Collaborative Development: The Old Good Time Basic problems: Several persons working on the same set of files 1 “Hey, you’ve modified the same file as me, how do we merge?”, 2 “Your modifications are broken, your code doesn’t even compile. Fix your changes before sending it to me!”, 3 “Your bug fix here seems interesting, but I don’t want your other changes”. Historical solutions: I Never two person work at the same time. When one person stops working, (s)he sends his/her work to the others. ⇒ Doesn’t scale up! Unsafe. I People work on the same directory (same machine, NFS, . ) ⇒ Painful because of (2) above. I People lock the file when working on it. ⇒ Doesn’t scale up! Matthieu Moy (CSA/IISc) DVC October 2006 < 6 / 43 > Prehistory History Linux Bazaar Conclusion Collaborative Development: The Old Good Time Basic problems: Several persons working on the same set of files 1 “Hey, you’ve modified the same file as me, how do we merge?”, 2 “Your modifications are broken, your code doesn’t even compile. Fix your changes before sending it to me!”, 3 “Your bug fix here seems interesting, but I don’t want your other changes”. Historical solutions: I Never two person work at the same time. When one person stops working, (s)he sends his/her work to the others. ⇒ Doesn’t scale up! Unsafe. I People work on the same directory (same machine, NFS, . ) ⇒ Painful because of (2) above. I People lock the file when working on it. ⇒ Doesn’t scale up! I People work trying to avoid conflicts, and merge later. Matthieu Moy (CSA/IISc) DVC October 2006 < 6 / 43 > Common ancestor #include <stdio.h> int main () { printf("Hello"); return 0; } Tools like diff3 can solve this Merging relies on history! Collaborative development linked to backups Prehistory History Linux Bazaar Conclusion Merging: Problem and Solution My version Your version #include <stdio.h> #include <stdio.h> int main () { int main () { printf("Hello"); printf("Hello!\n"); return EXIT_SUCCESS; return 0; } } Matthieu Moy (CSA/IISc) DVC October 2006 < 7 / 43 > Tools like diff3 can solve this Merging relies on history! Collaborative development linked to
Load more

Recommended publications
  • Efficient Algorithms for Comparing, Storing, and Sharing
    EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY May 2012 Major Subject: Computer Science EFFICIENT ALGORITHMS FOR COMPARING, STORING, AND SHARING LARGE COLLECTIONS OF EVOLUTIONARY TREES A Dissertation by SUZANNE JUDE MATTHEWS Submitted to the Office of Graduate Studies of Texas A&M University in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY Approved by: Chair of Committee, Tiffani L. Williams Committee Members, Nancy M. Amato Jennifer L. Welch James B. Woolley Head of Department, Hank W. Walker May 2012 Major Subject: Computer Science iii ABSTRACT Efficient Algorithms for Comparing, Storing, and Sharing Large Collections of Evolutionary Trees. (May 2012) Suzanne Jude Matthews, B.S.; M.S., Rensselaer Polytechnic Institute Chair of Advisory Committee: Dr. Tiffani L. Williams Evolutionary relationships between a group of organisms are commonly summarized in a phylogenetic (or evolutionary) tree. The goal of phylogenetic inference is to infer the best tree structure that represents the relationships between a group of organisms, given a set of observations (e.g. molecular sequences). However, popular heuristics for inferring phylogenies output tens to hundreds of thousands of equally weighted candidate trees. Biologists summarize these trees into a single structure called the consensus tree. The central assumption is that the information discarded has less value than the information retained. But, what if this assumption is not true? In this dissertation, we demonstrate the value of retaining and studying tree collections.
    [Show full text]
  • Distributed Configuration Management: Mercurial CSCI 5828 Spring 2012 Mark Grebe Configuration Management
    Distributed Configuration Management: Mercurial CSCI 5828 Spring 2012 Mark Grebe Configuration Management Configuration Management (CM) systems are used to store code and other artifacts in Software Engineering projects. Since the early 70’s, there has been a progression of CM systems used for Software CM, starting with SCCS, and continuing through RCS, CVS, and Subversion. All of these systems used a single, centralized repository structure. Distributed Configuration Management As opposed to traditional CM systems, Distributed Configuration Management Systems are ones where there does not have to be a central repository. Each developer has a copy of the entire repository and history. A central repository may be optionally used, but it is equal to all of the other developer repositories. Advantages of Distributed Configuration Management Distributed tools are faster than centralized ones since metadata is stored locally. Can use tool to manage changes locally while not connected to the network where server resides. Scales more easily, since all of the load is not on a central server. Allows private work that is controlled, but not released to the larger community. Distributed systems are normally designed to make merges easy, since they are done more often. Mercurial Introduction Mercurial is a cross-platform, distributed configuration management application. In runs on most modern OS platforms, including Windows, Linux, Solaris, FreeBSD, and Mac OSX. Mercurial is written 95% in Python, with the remainder written in C for speed. Mercurial is available as a command line tool on all of the platforms, and with GUI support programs on many of the platforms. Mercurial is customizable with extensions, hooks, and output templates.
    [Show full text]
  • Higher Inductive Types (Hits) Are a New Type Former!
    Git as a HIT Dan Licata Wesleyan University 1 1 Darcs Git as a HIT Dan Licata Wesleyan University 1 1 HITs 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory 2 Generator for 2 equality of equality HITs Homotopy Type Theory is an extension of Agda/Coq based on connections with homotopy theory [Hofmann&Streicher,Awodey&Warren,Voevodsky,Lumsdaine,Garner&van den Berg] Higher inductive types (HITs) are a new type former! They were originally invented[Lumsdaine,Shulman,…] to model basic spaces (circle, spheres, the torus, …) and constructions in homotopy theory But they have many other applications, including some programming ones! 2 Generator for 2 equality of equality Patches Patch a a 2c2 diff b d = < b c c --- > d 3 3 id a a b b
    [Show full text]
  • DVCS Or a New Way to Use Version Control Systems for Freebsd
    Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions DVCS or a new way to use Version Control Systems for FreeBSD Ollivier ROBERT <[email protected]> BSDCan 2006 Ottawa, Canada May, 12-13th, 2006 Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions Agenda 1 Brief history of VCS 2 FreeBSD context & gures 3 Is Arch/baz suited for FreeBSD? 4 Mercurial to the rescue 5 New processes & policies needed 6 Conclusions Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions The ancestors: SCCS, RCS File-oriented Use a subdirectory to store deltas and metadata Use lock-based architecture Support shared developments through NFS (fragile) SCCS is proprietary (System V), RCS is Open Source a SCCS clone exists: CSSC You can have a central repository with symlinks (RCS) Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions CVS, the de facto VCS for the free world Initially written as shell wrappers over RCS then rewritten in C Centralised server Easy UI Use sandboxes to avoid locking Simple 3-way merges Can be replicated through CVSup or even rsync Extensive documentation (papers, websites, books) Free software and used everywhere (SourceForge for example) Ollivier ROBERT <[email protected]> DVCS or a new way to use Version Control Systems for FreeBSD Brief history of VCS FreeBSD context & gures Is Arch/baz suited for FreeBSD? Mercurial to the rescue New processes & policies needed Conclusions CVS annoyances and aws BUT..
    [Show full text]
  • New York Software Symposium New York Information Technology Center June 24 - 25, 2011
    New York Software Symposium New York Information Technology Center June 24 - 25, 2011 Fri, Jun. 24, 2011 Room 2 Room 3 Room 4 Room 5 Room 6 8:00 - 9:00 AM REGISTRATION/BREAKFAST/WELCOME 9:00 - 10:30 AM Slimmed Down Software: Busy Java Developer&apos;s Sonar: Code Quality Programming HTML5 Concurrency without A Lean Approach Guide to Java 7 Metrics Made Easy Tim Berglund pain in pure Java Hamlet D`Arcy Ted Neward Matthew McCullough Venkat Subramaniam 10:30 - 11:00 AM BREAK 11:00 - 12:30 PM New Ideas for Old Code Busy Java Developer&apos;s Open Source Debugging NoSQL Smackdown! Collections for Concurrency Hamlet D`Arcy Guide to Games Tools for Java Tim Berglund Venkat Subramaniam Ted Neward Matthew McCullough 12:30 - 2:30 PM LUNCH & KEYNOTE 2:30 - 4:00 PM Pragmatic Architecture Java Boilerplate Busters Cascading through Hadoop: A Getting Started with Grails Programming in Functional Style Ted Neward Hamlet D`Arcy DSL for Simpler MapReduce Tim Berglund Venkat Subramaniam Matthew McCullough 4:00 - 4:30 PM BREAK 4:30 - 6:00 PM How to Select and Architectural Kata Workshop Resource-Oriented Cassandra: Radical Scala for the Intrigued Adopt a Technology Ted Neward Architectures : REST I NoSQL Scalability Venkat Subramaniam Peter Bell Brian Sletten Tim Berglund New York Software Symposium New York Information Technology Center June 24 - 25, 2011 Sat, Jun. 25, 2011 Room 2 Room 3 Room 4 Room 5 Room 6 8:00 - 9:00 AM BREAKFAST 9:00 - 10:30 AM Cryptography on the Resource-Oriented Integrating JVM Languages Complexity Theory and Busy Java Developer&apos;s
    [Show full text]
  • Git Basics Git Expertise
    Overview Git basics Git expertise Git A GNU Alternative to Bitkeeper Mohamed Barakat University of Kaiserslautern ITWM Kaiserslautern, January 2010 Mohamed Barakat Git Overview Git basics Git expertise 1 Git basics The Git configuration file Create a Git-repository Using a Git-repository 2 Git expertise Branching Pulling Merging and Cherry-Picking Mohamed Barakat Git Overview The Git configuration file Git basics Create a Git-repository Git expertise Using a Git-repository Overview 1 Git basics The Git configuration file Create a Git-repository Using a Git-repository 2 Git expertise Branching Pulling Merging and Cherry-Picking Mohamed Barakat Git Overview The Git configuration file Git basics Create a Git-repository Git expertise Using a Git-repository Git working copy and Git-repsoitory Git is a distributed SCM Git is a distributed Source Code Management system (SCM), i.e. each Git working copy sits on top of its own local Git repository located in a single top-level subdirectory .git. SVN is in contrast to Git a centralized SCM system, i.e. the SVN-repository is on exactly one server. Git allows you to commit, checkout, reset, etc. without contacting a server! Mohamed Barakat Git Overview The Git configuration file Git basics Create a Git-repository Git expertise Using a Git-repository The configuration file ˜/.gitconfig Create a Git configuration file vi ˜/.gitconfig [svn] authorsfile = .git/info/svn-authors [color] diff = auto status = auto branch = auto [user] name = Firstname Lastname email = [email protected] Mohamed Barakat Git Overview The Git configuration file Git basics Create a Git-repository Git expertise Using a Git-repository Create a Git-repository (quick version) init, add, commit Create a Git-repository in the directory XY: 1 cd XY 2 git init 3 git add .
    [Show full text]
  • Darcs 2.0.0 (2.0.0 (+ 75 Patches)) Darcs
    Darcs 2.0.0 (2.0.0 (+ 75 patches)) Darcs David Roundy April 23, 2008 2 Contents 1 Introduction 7 1.1 Features . 9 1.2 Switching from CVS . 11 1.3 Switching from arch . 12 2 Building darcs 15 2.1 Prerequisites . 15 2.2 Building on Mac OS X . 16 2.3 Building on Microsoft Windows . 16 2.4 Building from tarball . 16 2.5 Building darcs from the repository . 17 2.6 Building darcs with git . 18 2.7 Submitting patches to darcs . 18 3 Getting started 19 3.1 Creating your repository . 19 3.2 Making changes . 20 3.3 Making your repository visible to others . 20 3.4 Getting changes made to another repository . 21 3.5 Moving patches from one repository to another . 21 3.5.1 All pulls . 21 3.5.2 Send and apply manually . 21 3.5.3 Push . 22 3.5.4 Push —apply-as . 22 3.5.5 Sending signed patches by email . 23 3.6 Reducing disk space usage . 26 3.6.1 Linking between repositories . 26 3.6.2 Alternate formats for the pristine tree . 26 4 Configuring darcs 29 4.1 prefs . 29 4.2 Environment variables . 32 4.3 General-purpose variables . 33 4.4 Remote repositories . 34 3 4 CONTENTS 4.5 Highlighted output . 36 4.6 Character escaping and non-ASCII character encodings . 36 5 Best practices 39 5.1 Introduction . 39 5.2 Creating patches . 39 5.2.1 Changes . 40 5.2.2 Keeping or discarding changes . 40 5.2.3 Unrecording changes .
    [Show full text]
  • Collaboration Tools in Software Engineering Stepan Bolotnikov Me
    Collaboration Tools in Software Engineering Stepan Bolotnikov Me ● Stepan Bolotnikov ● Software Engineer at Guardtime ● MSc in Software Engineering from UT, 2018 ● [email protected] You Mostly BSc students in Computer Science ● Software developers / QA engineers ● CS researchers ● Project managers / team leads In any case connected to software projects, sharing knowledge and resources Course ● History and working principles of version control systems (VCS) ● Git distributed VCS ● Issue tracking ● Theoretical knowledge + practical hands-on exercises ● 8 sessions ● Every 2nd Friday ● Lecture + practice ● Non-differentiated (pass/fail) Schedule ● 22. Feb - Introduction, history of VCS ● 08. Mar - Introduction to Git, setting up the first repository, basic Git usage ● 22. Mar - Common Git commands ● 05. Apr - Branching in Git, common branching models ● 19. Apr - Troubleshooting common Git issues ● 03. May - Github; Issue tracking ● 17. May - Advanced Git usage; git hooks and CI ● 31. May - Guest lecture, preparation for exam ● 07. June - Exam 1 ● 14. June - Exam 2 Sessions ● 4h ● Lecture part ● Practical part Final exam ● 7th or 17th June ● Individual practical tasks ● “Poor”, “Satisfactory” or “Good” ● “Satisfactory” and “Good” - passing In order to pass the course ● Active participation in at least 6 out of 8 sessions ○ Complete the practical tasks ● “Satisfactory” or “Good” on the final exam Communication Course website http://courses.cs.ut.ee/2019/cse Course Slack Click Lecture 1: Introduction to course, History of Version
    [Show full text]
  • Experten-Dossier 2019
    Experten-Dossier 2019 Über 80 Seiten mit praxisorientiertem Wissen für .NET-Entwickler rund um .NET Core, Azure DevOps, TypeScript, Cosmos DB, ML.NET, Git und Azure! bastacon www.basta.net Inhalt Agile & DevOps Die DevOps-Challenge 4 DevOps-Fallstricke und wie man ihnen entkommen kann von Kevin Gerndt Microservices & APIs Warum einfach? Es geht auch komplex! 10 Entwicklung von Microservices mit Microsoft .NET von Dr. Felix Nendzig Go Git! 16 Git erobert die Entwicklerwelt von Uwe Baumann Des Kaisers neue Kleider 21 Aus VSTS wird Azure DevOps – mehr als nur ein neuer Name? von Nico Orschel und Thomas Rümmler .NET Framework & C# R. I. P .NET „Core“ 29 .NET Framework, .NET Core und Mono sind tot – lang lebe .NET 5.0! von Dr. Holger Schwichtenberg Machine Learning für die Zukunft 33 Hintergrund und Einstieg in ML mit .NET von Kevin Gerndt Architektur Kolumne: Stropek as a Service 40 Zehn Hausaufgaben für die Cloud-Architektur – Eine gute Softwarearchitektur setzt klare Ziele voraus von Rainer Stropek Große Business-Apps mit Angular meistern 43 Nachhaltige Angular-Architekturen mit Nx und Strategic Design von Manfred Steyer Inhalt Sicherheit Du kommst hier nicht rein 48 API Authorization in ASP.NET Core 3.0 mit IdentityServer von Sebastian Gingter Wasm – Ist das sicher oder kann das weg? 53 Neue Besen kehren gut, sagt man. Aber sind sie auch sicher? von Carsten Eilers HTML5 & JavaScript Das Beste aus zwei Welten 59 Mit ASP.NET Core und Angular eine Webanwendung erstellen von Fabian Gosebrink Injections für echte TypeScript-Junkies 70 Dependency
    [Show full text]
  • Everything You Need to Know About Openjdk's Move to Git and Github
    Menu Topics Archives Downloads Subscribe Everything you need to know JAVA 17 about OpenJDK’s move to Git and GitHub Everything you need to know Blame or thank BitKeeper about OpenJDK’s move to Git Why not Mercurial? and GitHub Why Git? Why GitHub? Why the move, and why now? The move from Mercurial to Git Getting the source code and provided an opportunity to consolidate building the OpenJDK the source code repositories. Conclusion by Ian Darwin Dig deeper May 14, 2021 Download a PDF of this article Have you ever built your own Java Development Kit from source? Most end users of the JDK will not need to build their own JDK from the Oracle source code. I’ve needed to do that only a few times when I was running on the OpenBSD UNIX-like system, which is not one of the three supported platforms. Sure, you might want to build your own JDK to try out a new feature that you think should be added to Java. You might choose to build from source to be sure you are running a more trustworthy binary. Having the complete source code readily available, and now in a more commonly used download format, means it is easier than ever to build your own JDK. Yes, it’s a better-documented, easily configured process than in the past. But it’s still a bit confusing. The source code for the OpenJDK recently moved from the Mercurial version control system (VCS) to the Git VCS and the GitHub repository system, and that’s probably a good thing.
    [Show full text]
  • Software Test and Performance, January 2006, Page 26
    A Publication P B RA E Un C ST it T T IC es ES ti : ng VOLUME 3 • ISSUE 1 • JANUARY 2006 • $8.95 www.stpmag.com XP’s Balanced Approach to Test Stressing Software With Open Source Tools A MMethodethod to Build Visibility Into Your DevelopmentDevelopment Process MakingMaking YourYour QAQA EEfffoforrttss FFlyly The Importance of Life Cycle Management A MESSAGE FROM THE EDITOR VOLUME 3 • ISSUE 1 • JANUARY 2006 Publisher Editorial Director Better Life Cycle Ted Bahr Alan Zeichick +1-631-421-4158 x101 +1-650-359-4763 [email protected] [email protected] Editor Director of Events Management Lindsey Vereen Donna Esposito [email protected] +1-415-785-3419 [email protected] Associate News Editor Everyone is familiar with the ground. While you Director of Circulation Alex Handy Agnes Vanek the rule of thumb that says can’t download a hard- [email protected] +1-631-421-4158 x111 at each step of the way, the ware patch, neither can [email protected] Art Director cost to fix a problem you get into a software LuAnn T. Palazzo Circulation Assistant increases tenfold, and hav- system with a wrench. [email protected] Advertising Traffic Phyllis Oakes ing to fix a problem in the And getting to the site Copy Editor +1-631-421-4158 x115 field is the most expensive. can pose a challenge. George Ellis [email protected] [email protected] (Granted, the Internet It is an unfortunate fact Office Manager/ somewhat mitigates the of life that despite lofty Contributing Editors Marketing Scott Barber Cathy Zimmermann cost of patches for de- intentions, test cycles will [email protected] [email protected] ployed software, but still, Lindsey Vereen always get truncated.
    [Show full text]
  • Software Development a Practical Approach!
    Software Development A Practical Approach! Hans-Petter Halvorsen https://www.halvorsen.blog https://halvorsen.blog Software Development A Practical Approach! Hans-Petter Halvorsen Software Development A Practical Approach! Hans-Petter Halvorsen Copyright © 2020 ISBN: 978-82-691106-0-9 Publisher Identifier: 978-82-691106 https://halvorsen.blog ii Preface The main goal with this document: • To give you an overview of what software engineering is • To take you beyond programming to engineering software What is Software Development? It is a complex process to develop modern and professional software today. This document tries to give a brief overview of Software Development. This document tries to focus on a practical approach regarding Software Development. So why do we need System Engineering? Here are some key factors: • Understand Customer Requirements o What does the customer needs (because they may not know it!) o Transform Customer requirements into working software • Planning o How do we reach our goals? o Will we finish within deadline? o Resources o What can go wrong? • Implementation o What kind of platforms and architecture should be used? o Split your work into manageable pieces iii • Quality and Performance o Make sure the software fulfills the customers’ needs We will learn how to build good (i.e. high quality) software, which includes: • Requirements Specification • Technical Design • Good User Experience (UX) • Improved Code Quality and Implementation • Testing • System Documentation • User Documentation • etc. You will find additional resources on this web page: http://www.halvorsen.blog/documents/programming/software_engineering/ iv Information about the author: Hans-Petter Halvorsen The author currently works at the University of South-Eastern Norway.
    [Show full text]