Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am in need of preparing powerpoint slides to discuss Trac Workflow.
I caught hold of "One Laptop per Child" (olpc) Trac Workflow and impressed by the workflow it follows.Can anyone Help me with this:
1. Do olpc follows default workflow which trac comes with default?
2. Any links or hint where I can find resources for further explanation of each roles of Maintainer,coder,builder,releaser etc..
My Team has agreed with olpc Concept. I have also created a Powerpoint Slides for the same.
Anonymous Alice -- generic (possibly minimally skilled) Trac user.
Terry Ticket-Herder -- ticket herder who watches incoming tickets and improves their quality.
Carol Coder -- coder who diagnoses, designs, codes, and reviews code.
Mark Maintainer -- module maintainer (packager) aggregates code and pushes it into build streams (i.e. into Fedora or Joyride).
Release Rob -- release team member who approves requests to modify a stable build stream.
Bill Builder -- build team member
Quality Assurance -- QA team member
Anonymous Alice observed curious behavior while exploring the system. She records it in Trac but does not set the next_action field or sets it to unknown.
Terry Ticket-Herder decides Alice's reported behavior is significant but doesn't know how to reproduce it so he changes the next_action to reproduce to indicate his need for instructions on how to reproduce the issue.
Terry might instead have closed Alice's ticket as invalid, worksforme, etc or have sent it on to a later state if Alice wrote a particularly good ticket.
If necessary, Terry would also fill in the Milestone, Component, Keywords, and CC fields to conform to our Trac conventions.
Once Alice's behavior can be reproduced, it can be diagnose[d] by Carol Coder (probably with help from Alice).
Carol will eventually propose a design that she thinks will resolve the issue.
Carol will code to her design and will seek review of her work. She will also write a testcase.
When all is in order, Carol or Mark Maintainer will package the changes and add them to a development build (in the add to build state).
When built in Joyride, Carol or Mark will test in build.
If the test fails, then the tester may remand the issue to an earlier state and owner; otherwise, the tester should advance the ticket to the next state (see below).
Test results should be recorded according to the Trac conventions (e.g as a keyword like joyride-2230:+ for a 'pass' or 8.2-757:- for a 'fail').
During change control, changes must pass through three additional steps:
Changes cannot be committed to the stable build stream without meeting basic requirements. Release Rob will regularly review tickets in the approval for release state.
Approved changes will be sent to the Bill Builder in the add to release state.
Once Bill updates the stable build stream, he will place the ticket in the test in release state for further testing by Alice, Carol, or another friend.
After being tested as fixed in a release-stream build, issues should be pushed through some of the qa signoff, finalize, or no action states. See below.
Occasionally, an issue may require test facilities beyond those available to ordinary developers and testers or may be so important that it requires additional systematic testing. Such issues can be pushed, at anyone's discretion, through the qa signoff state where Quality Assurance will examine them and pass them on.
Rob will document tickets which reach the finalize state in the Release Notes.
Tickets will eventually require no action.
Rob is responsible for closing user-facing issues which result in changes to the build or work-arounds.
Other issues can be closed by anyone when they cease to be relevant to the release proces