[[Category:SBR600]]Software build and release is the process of building (compiling, testing, and packaging) software for further testing or in preparation for release, and the release and distribution of the built software and updates. This course is a professional option in the [http://scs.senecacollege.ca/ Seneca School of Information and Communication Technology] [https://scs.senecac.on.ca/cty CTY ] program. It will be has been offered for the first time in since January, 2009.  == SBR600 in Fall 2013 == In SBR600, you'''Watch ll be working directly with the Fedora project and other open source communities, on various build and release projects. This semester, most projects will focus on improvements to [http://pidora.ca Pidora], a [[:fedora:Fedora Remix|Fedora Remix]] for updates the [http://raspberrypi.org Raspberry Pi]. Note that, unlike some other project-based courses, the results of the projects done in SBR600 will be incorporated into Pidora, the Fedora project, or other open source projects, and have a real impact on other people. For this page as reason, projects must be completed in collaboration with the relevant open source communities, using relevant [[SBR600 Communication Tools|communication tools]]. Work performed in this course outline will be licensed using the relevant open source licenses used by the associated community. Working in an open source community provides the opportunity to build solid real-world experience, your technical skills and reputation, and a network of contacts, all of which are useful in developing your career. === Course Materials === * Course information and other details labs are finalizedonline.* You will require access to a personal Fedora 18 or Fedora 19 installation. This may be on your own laptop, on a virtual machine on your laptop, on an SSH-accessible system (such as a home desktop computer), or on a SATA disk pack or USB drive for use with the Seneca computers.'''* Recommended (optional): [[Purchase a Raspberry Pi]]

= Course Description == Professor ===

Software Build and Release creates reliable, replicable processes to turn source code and related inputs into ready-to-run software. These critical systems are used in software development companies, IT departments, and Open Source projects, and are highly automated through the use of scripting languages such as Bash, Perl, and Python. Students will learn to manage the Build and Release process SBR600 is taught by selecting, installing, configuring, customizing, and maintaining a variety of build tools. This is a project-based course, and students will work within an established Open Source community. The particular open source community or communities to be studied will vary with each offering and be announced at the beginning of the semester[[User:Chris Tyler|Chris Tyler]].

== Prerequisites = Succeeding in SBR600 ===OPS335 & OPS435

== Specific Outcomes ==Upon successful completion of There are three keys to success in this subject students should be able tocourse:* Describe the Build and Release process.* Discuss the infrastructure necessary to support Build and Release.* Write scripts for build automation and testing.* Discuss the issues and current trends in build and release infrastructure and technology.* Discuss the human and technical challenges inherent in the build and release process.* Select, install, configure, customize, and maintain a variety of tools for building, testing, composing, packaging, and distributing software.* Develop virtualized, parallel, distributed, cloud, and grid computing strategies for build and release.* Work collaboratively with fellow students and, where possible, members of the open source community.

== Topic Outline ==* Overview of 1. '''Work ''in'' the Build open source community.''' The projects we will be doing are too large and Release process - 10%** Goals too unfamiliar for you to succeed entirely on your own. You will need to use the community's knowledge, connections, and scope of resources to succeed well. Respect the Build and Release process** Creating community's standards, tell the infrastructure** Automation*** Scripting*** Scheduling** Securitycommunity what you're doing, replicabilityask when you have a question, and process integrity* Basic Build Concepts - 30%** make** Version control systems*** Branching*** Tagging** Automated testing** Composing and packaging** Distributing released software** Handling multiple platforms** Scripted build processes* Server farms and distributed processing - 30%** Multiple target platforms** Computing platforms*** Parallel computing*** Distributed computing*** Grid computing*** Cloud computing* Supporting technologies - 20%** Virtualization*** Scripted control of virtual machines** Monitoring and management technologies* Working with Open Source communities - 10%** Communication** Collaboration** Managing public access to infrastructurepull your own weight within the community.

== Modes Of Instruction ==* Two hours interactive lecture per week2. '''Blog.''' Tell your professor, your colleagues, the community, and everyone else what you're doing. Write a lot and write well, include good technical content, and incorporate links to all relevant resources and the product of your work, and two hours activity-based learning per week (four hours total) write often. Almost all of your work in this course is submitted by blogging.

== Reference Material Weekly Outline ==* TBA

=Course Outline = Promotion Policy ==To obtain a credit in this subject, a student must: * Achieve a grade of 55% or better on the overall course* Achieve a grade of 55% or better on the project deliverables