Changes

|<div style="background:#ffff00">[[Fall 2010 2013 SBR600 Weekly Schedule|Weekly Schedule]]</div>[[Fall 2013 SBR600 Participants|Participants and Project Table]]<br/>[[Fedora ARM Secondary ArchitectureSBR600 Potential Projects|Potential Project List]]<br />[[Fall 2013 SBR600 Presentation Schedule|Release Presentation Schedule]]<br />[https://scs.senecac.on.ca/course/sbr600 Course Outline]<br />[[Fedora ARM Secondary Architecture]]<br />[http://pidora.ca Pidora]<br />[http://fedoraproject.org Fedora Project]<br />[http://docs.fedoraproject.org/ Fedora documentation]<br />[http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT]<br />[http://koji.fedoraproject.org Fedora Koji]<br />[http://koji.pidora.ca Pidora Koji]

{{Admon/important|Course Availability|This course has been temporarily replaced by [[Category:SBR600SPO600|SPO600 Software Portability and Optimization]]This is to take advantage of the unique learning opportunity presented by the emergence of a professional option in the CTY programnew architecture: 64-bit ARM. It has been offered since January 2009We anticipate offering SBR600 at a future date.}}

== Software Build and Release - SBR600 in Fall 2010 ==

This semester, students will be working directly with the Fedora project, on various build and release projects. Some of this work will be centered on the [[Fedora ARM Secondary ArchitectureCategory:SBR600]] project started by Software build and release is the January 2010 SBR600 classprocess of building (compiling, testing, and packaging) software for further testing or in preparation for release, and the rest release and distribution of the projects will focus on other aspects of the Fedora build process. The skills required will vary according to the project selectedbuilt software and updates.

Note that, unlike some other project-based courses, the results of the projects done in SBR600 will be incorporated into the Fedora project (or other open source projects) and have This course is a real impact on other people. For this reason, projects must be completed professional option in collaboration with the relevant open source communities, using relevant [[SBR600 http://scs.senecacollege.ca/ Seneca School of Information and Communication Tools|communication toolsTechnology][https://scs.senecac.on.ca/cty CTY]program. Work performed in this course will be licensed using the relevant open source licenses used by the associated communityIt has been offered since January 2009.

=== Course Materials =SBR600 in Fall 2013 ==

Students will require access to a personal In SBR600, you'll be working directly with the Fedora installationproject and other open source communities, either on their own laptopvarious build and release projects. This semester, most projects will focus on a virtual machine on their laptopimprovements to [http://pidora.ca Pidora], or on a SATA disk pack[[:fedora:Fedora Remix|Fedora Remix]] for the [http://raspberrypi.org Raspberry Pi].

=== Succeeding 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 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 will be licensed using the relevant open source licenses used by the associated community.

There 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 two keys to success useful in this course:developing your career.

2* Course information and labs are online. '''Blog* You will require access to a personal Fedora 18 or Fedora 19 installation.''' Tell This may be on your professorown laptop, on a virtual machine on your colleagues, the communitylaptop, and everyone else what you're doing. Write wellon an SSH-accessible system (such as a home desktop computer), include good technical content, and incorporate links to all relevant resources and or on a SATA disk pack or USB drive for use with the product of your workSeneca computers.* Recommended (optional): [[Purchase a Raspberry Pi]]

SBR600 is taught by [[User:Chris Tyler|Chris Tyler]] (Fall 2010).

== [[Fall 2010 SBR600 Weekly Schedule|Weekly Outline]] == See the [[Fall 2010 Succeeding in SBR600 Weekly Schedule]] for specific dates and topics. = Course Description = 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 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. == Prerequisites ==[https://scs.senecac.on.ca/course/ops335 OPS335] & [https://scs.senecac.on.ca/course/ops435 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