1,885
edits
Changes
SBR600
,no edit summary
!style="background: #cccccc"| Quick Links
|-
|<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 [[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 has been offered since January 2009. == SBR600 in Fall 2013 ==
=== Course Materials ===
=== Professor ===
SBR600 is taught by [[User:Chris Tyler|Chris Tyler]] (Fall 2010).
=== Succeeding in SBR600 ===
There are two three keys to success in this course: 1. '''Work in the open source community.''' The projects we will be doing are too large and too unfamiliar for you to succeed entirely on your own. You will need to use the community's knowledge, connections, and resources to succeed well. Respect the community's standards, tell the community what you're doing, ask when you have a question, and pull your own weight within the community. 2. '''Blog.''' Tell your professor, your colleagues, the community, and everyone else what you're doing. Write well, include good technical content, and incorporate links to all relevant resources and the product of your work. Most of your work in this course are submitted by blogging. == [[Fall 2010 SBR600 Weekly Schedule|Weekly Outline]] == See the [[Fall 2010 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 this subject students should be able to:* 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.
== 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