1,885
edits
Changes
SBR600
,no edit summary
{| style="float: right; margin: 0 0 3em 2em; border: 1px solid black;"
!style="background: #cccccc"| Quick Links
|-
|<div style="background:#ffff00">[[Fall 2013 SBR600 Weekly Schedule|Weekly Schedule]]</div>[[Fall 2013 SBR600 Participants|Participants and Project Table]]<br />[[SBR600 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 [[SPO600|SPO600 Software Portability and Optimization]] to take advantage of the unique learning opportunity presented by the emergence of a new architecture: 64-bit ARM. We anticipate offering SBR600 at a future date.}}
= Software Build and Release - SBR600 =
[[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.
== Professor SBR600 in Fall 2013 ==
=== Course Description Materials ===
== Prerequisites = Professor ===OPS335 & OPS435
== Topic Outline = Succeeding in SBR600 ===* Overview of the Build and Release process - 10%** Goals and scope of the Build and Release process** Creating the infrastructure** Automation*** Scripting*** Scheduling** Security, replicability, 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 infrastructure
== Promotion Policy Weekly Outline ==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
= Links Course Outline =